In this thread: people who believe the myth of the safe C programmer. The one who has memorized the spec and is able to hold endless context in their brain while writing code. They themselves are C compilers.
post
there doesn't seem to be anything here
19 comments in c/linux@programming.dev view that post
replies:
I think it's time for this instance to consider introducing a filter where users have to choose a language they know (any language), and then have to answer easy questions about it (in a specific way), before being able to post here.
It can be limited to specific posts, to limit the false-negative filtering of genuine discourse.
This should help with bots, or worse, actual humans who accepted being shaped into acting like ones. The line separating the two has become very thin anyway, given the prevalence of LLM use, both automatic AND manual.
If only there were a few alternatives to Rust for system development with a syntax that isn't a marriage of flesh between OCaml and C. Unfortunately none exists, because if I say otherwise, rustacerans will accuse me of "FUDposting", and some will even try to dig up some dirt about me, to ruin my life and to ultimately force me off the web, because shame is good, except if they're the target of said shame.
So we're left with a language that:
- Was marketed as a functional programming language until people started to "FUDpost" about how functional programming has its own issues (optimization, etc.), so the Rust team quickly tried to course correct and market it as a "multi paradigm" language. It is "FUD" if you ask why it's still const by default. If only Oracle found out about this tactic, to market Java as a "multi paradigm programming language", because you can just "opt out from OOP aspects", then tell its usiers that "packaging classes are just good practice".
- Makes many optimizations very ugly if not impossible.
- Makes memory unsafe operations ugly, to "disintensivise the programmer from them".
- Has a pretty toxic userbase, which is only being called out by Lunduke-style toxic morons with anti-woke brainrot, and for the wrong reasons. No, the problem isn't that many people in the Rust community are often trans, and that the code of conduct aren't a selection of Bible-verses, but that a portion of Rust users weaponize callouts, with this callout weaponization actually coming from 4chan and other sites that pioneered networked harassment.
replies:
plenty more fish in the sea
replies:
3 comments in c/news@lemmy.linuxuserspace.show view that post
Sounds like a healthy move. Of course, now they need to promote a few reviewers to maintainers to replace those who have left / are leaving.
You know a project has truly matured when the original maintainers can all walk away and the project can carry on without them.
Sad to see Mr. Gaynor step down
replies:
no comments (yet)