mstdn.starnix.network is one of the many independent Mastodon servers you can use to participate in the fediverse.
Starnix is a Fediverse/ActivityPub Focused platform. Topics are mainly Technology and computer related but are not required to fall into those categories.

Server stats:

26
active users

THE MARTYR OF BUTLERIAN JIHAD

There is this one peculiar feature of the culture surrounding C and C++ languages that I am yet to witness anywhere else. JavaScript might just be coming close, but even it isn't there yet. Many - if not most - professional C and C++ programmers treat compiler as their adversary, they also often openly despise compiler writers. How often have you seen someone complaining, that a new version of GCC broke his code? And I do not refer to bugs in the compiler, those may happen in any ecosystem. No, this is a very interesting quality of C and C++, with their rather vague and vacuous description allowing a whole lot of leeway in compiler implementations. This goes in a rather stark contrast with languages like Haskell or the Lisp family, where the compiler is a programmer's best friend, providing a whole lot of insight on the code behaviour.

To add to that, I have also seen a lot of hatred towards the standards of the aforementioned languages from C and C++ programmers, despite these same people praising the idea of their languages being standardised (as opposed to, say, Rust). Most of these specialists have never even bothered to read the standards for their favourite languages. And this results in often dire consequences. To be honest, reading GCC Bugzilla is one of my favourite pastimes, just so much anger is being thrown around.

A article by David Chisnall states that C is actually three different languages. There is the C that programmers know (or they think they know), there is the C as it is described in the standard, and there is the C implemented into compilers. And these are at times rather different languages altogether, with the first one often being completely not like the other two. The point also applies to C++.

@icon_of_computational_sin
> How often have you seen someone complaining, that a new version of GCC broke his code?
Python isn't a compiled language, at least not in the classic sense, but if I were doing commercial Python development, I'd be complaining about it quite often: from what I've seen, they have changed the way asynchronous stuff works at least three times. To be fair, they've been changing the syntax too, which depending on what you expected to happen might piss you even more or less.
> where the compiler is a programmer's best friend, providing a whole lot of insight on the code behaviour
Rust is exactly like that. Despite being more like C and C++ its compiler actually gives you valuable advice and even prevents potentially problematic shit from being compiled at all. In addition to that its standard is its implementation. It's still formalised, but at least standardisation isn't something being done offshore.
And you still don't like it! 😂
Problem with striped socks? 😏

@m0xEE no, my problem with Rust mainly lies in that most of the code in it is garbage. If you grep ".unwrap()" on any Rust project, you'll see at least a dozen results, and every single one of those is an abort() call waiting to happen. What good is a language that saves you from stupid memory mistakes only to force you to shoot yourself in the foot in an entirely different matter?
This is why most Rust libraries on crates.io are pure garbage.