mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

811
active users

#programming

573 posts360 participants16 posts today
Replied in thread

@screwtape
However, the workaround, so that you need not wait an unbounded and unguessable amount of time, is to go to the post's home server.

(The post is about "I like all #programming languages but I have only a few that are my favourites. #Smalltalk is one of those few. But all the current open-source implementations still sport that Smalltalk-80, last-Century chic look....[back then Smalltalk] looked positively fresh, futuristic, and fun. But that look is now 45 years old." Etc.)

In the hopefully unlikely absence of still further errors, it should then be immediately readable -- although I believe *replying* to such a thing still results in that remote-to-you server telling your Mastodon client to take you back to your home server to make the reply.

I forget if I always have to actually follow the person who posted as an additional step in that reply.

I distrust frameworks.

They claim to speed up development by providing a clear and easy way of doing common tasks but a lot of the time they suffer from leaky abstractions or limitations which make it hard to do things that should be simple.

When you use a framework your problem often goes from "you missed a semicolon" to "ERROR IN library/awesome/framework/injector.hx: the widget dislikes the dongle" and have to spend 3 days figuring out that means you missed a semicolon

My timeline of #programming languages I only learned (") and used in production (*):

Basic (Vic-20/C64/PC)", Assembly (6502/6510)", Pascal", Cobol", Fortran", Ada", C/C++*, Assembly (x86)*, Java*, JavaScript*, C#*, Ruby*, Python*, PowerShell*, TypeScript*, F#", Bash*, Golang*

What does your programming language timeline look like?

RE: tooting.ch/@UrsEnzler/11434825

Tooting.ch [Swiss instance]Urs Enzler 🐉 (@UrsEnzler@tooting.ch)My timeline of programming languages I only learned (") and used in production (*): Turbo Pascal", Delphi*, Oberon", Java", ML", Prolog", C++*, Perl*, C#*, ColdFusion*, TypeScript*, F#* What does your programming language timeline look like?

Seeking help with some C++. I would like to have a templated class where I specify some template parameters inside <> brackets explicitly and the rest shall be deduced from the constructor parameters.

It works for regular functions, but not for constructors. Note that I can't use a regular function as the original problem stemmed from custom range objects.

Any ideas? Is it even possible?

godbolt.org/z/TdMK84WT7

Note: Ideally I would like T to be ...Ts, but if there is a solution for just a single T, then I expanding it to ...Ts is not that hard.

I like all #programming languages but I have only a few that are my favourites. #Smalltalk is one of those few. But all the current open-source implementations still sport that Smalltalk-80, last-Century chic look.

I learned the language on the XEROX Smalltalk-80 system, so this look-and-feel holds that certain nostalgic charm for me. And when we were all using the VT100 terminal, Smalltalk's bitmap graphics and MVC GUI looked positively fresh, futuristic, and fun. But that look is now 45 years old. My goodness, let us just get over those garish colours and serif fonts, already!

These days, #Pharo's look-and-feel is perhaps the least offensive to the modern eye. But even it has that mouldy, cheesy look.

I am perfectly happy to use the classic Smalltalk-80 language in its original form; its design is ageless. But I find no technical, economical, practical, or aesthetic justifications for retaining that 1980s' look-and-feel in the 2025 implementations.

Hacktical C
github.com/codr7/hacktical-c

"A practical hacker's guide to the C programming language.

In memory of Dennis Ritchie, one of the greatest hackers this world has known.

This book assumes basic programming knowledge. We're not going to spend a lot of time and space on explaining basic features, except where they behave differently in important ways compared to other mainstream languages. Instead we're going to focus on practical techniques for making the most out of the power and flexibility C offers."

A practical hacker's guide to the C programming language. - codr7/hacktical-c
GitHubGitHub - codr7/hacktical-c: A practical hacker's guide to the C programming language.A practical hacker's guide to the C programming language. - codr7/hacktical-c