Unless you work for the committee or for ISO somehow, then I don't think that really follows. C++ and JavaScript were both used in production for decades before they had standards, and the dissolution of the standards committee wouldn't cause compiler vendors to stop developing compilers.

I don't think it's fair to consider unsafe Rust such a small subset of the language that it requires calling it out as a separate thing from "Rust" in the title of an article. Unsafe constructs are necessary in the standard library and many crates, whether or not you use it in the code you actually write.

Doesn't prolog already "not work half the time"? (Disclaimer: I haven't used it.)

In case you're still interested in this type of resource, here's another one I just learned about: https://google.github.io/comprehensive-rust/

It's by the Android team at Google, and while it doesn't require knowledge of C++, it seems to be intended to bring devs up to speed on the concepts required for using Rust in Android and Chromium.

But do they actually have autonomy, give that random companies can use .io and .ai? Or did the British Indian Ocean Territory and Anguilla approve all such uses of those domains?

Why top-level, though? Why not amazon.in.com?

For what it's worth, WSL 2 with VSCode is actually great. Almost all the benefits of Linux (I still miss true tiling window management), with fewer weird driver issues.

That said, I generally just use whatever my company wants me to use, and I haven't worked somewhere that let us use native Linux boxes since 2014.

Modev says they've been using C for 25 years, and used Rust for several years as well! Their whole schtick baffles me.

Rust feels like entirely the wrong target for that sort of criticism, especially regarding "energy and resource intensity". Rust is well-known to be comparable to C in its efficiency.

I haven't told you to keep calm. I'm just confused about you repeating the same points, in the same words, over and over, even after being told that you don't have your facts correct.

I'm not saying you can't learn or talk about other languages; I'm confused by the mismatch between your posts criticizing people for promoting newer tech stacks and the ones where you seem to be promoting newer tech stacks yourself.

25 years of experience is certainly enough to have strong opinions, but until your last comment I had the impression that you had a year or less of experience in C, hence my question.

That's not a confession, it's a condemnation. It's not your fault that universities generally don't teach this stuff. (I think I had one lab session wherein we used valgrind.)