It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path
Technically you need a separate linter (errcheck) to ensure you don't just ignore errors. This is...not great. (That should have been a compiler error.)
I agree, but if you look at the specific email linked, it very clearly crosses the line into direct abuse, whereas most of Linus's rants do exist in a slightly greyer area (even if they'd be grounds for a discussion with HR at an actual company).
The second button is actually a pretty major change!
Why do you keep posting this exact same rant? I see that some posts are in different Lemmy communities and you've posted it at least once on hacker news, but you also posted it to this same community already (https://snac.bsd.cafe/modev/p/1727338529.193499) and, although I can't find it now, I remember you posting it months ago, too.
Several of your posts that aren't about how C is being "suppressed" (which the responses to your post have repeatedly demonstrated isn't true) are about how you, personally, are still learning C and want more resources to learn it. And now you're also posting about Nelua and Nim. This is wild to me! Why do you have such strong opinions about a language that you're still learning? If you're that passionate about C and believe that people should use it instead of newer languages, why do you care about Nim or Nelua? If you're just trolling, why do you engage relatively patiently in the comments? And whatever your goal is, why do you keep reposting the same rants, especially this one that's now quite old?
To be pedantic, I didn't ask a question, I just said I was surprised! I am still surprised.
For runtime reflection, no, you'd specifically be able to do things that would be impossible to optimize out.
But the proposal is actually for static (i.e. compile-time) reflection anyway, so the original performance claim is wrong.
But in the browser. My complaint with JavaScript is that it was effectively the only choice for in-browser logic up until WebAssembly was stabilized, and even now it requires JS glue code.
C is in no way "more for hobby developing and tooling". It's still foundational to compilers, language runtimes, and operating systems (the Linux kernel was, famously, exclusively written in C up until extremely recently, and the non-C parts are still optional). It's also the only supported language on many embedded devices.
One problem with this is that C is in no way the "roots" of programming; it's older than most of the languages we use today, but Fortran, Lisp, and Cobol are all older and are also still in use. (And of course there are other languages that predate C but have mostly fallen out of use, such as Pascal.) It feels "low-level" because it closely reflects the hardware for which it was originally designed, the PDP-7 and later the PDP-11. But in fact it hasn't truly been "low-level" for a long time: I highly recommend the ACM article "C Is Not a Low-level Language; Your computer is not a fast PDP-11."
The CLI is still pretty bad, and I say this as someone who's gotten so used to it that I find git GUIs more annoying than helpful.
log gets a random flag from diff, -p, that's incredibly useful but buried in the documentation. Printing a readable graph log requires magic incantations that aren't worth memorizing. git branch with no subcommand prints the list of branches, but to get similar behavior for git remote, you need to add -v. Etc.
I'm not sure where you're quoting from, but as far as I can see, only "Professional Engineer", "Licensed Engineer", and "Registered Engineer" are protected in the US.
Before Rust, the main argument I heard from C++ enthusiasts against Ada was that it was a nice idea but too "design-by-committee". Which, yeah, is an ironic thing for C++ fans to say, but I guess that was enough 🤷