In case anyone is looking for alternatives, there's a well-maintained fork of neofetch called hyfetch. There's also a neofetch clone written in C called fastfetch.
Using shift for erase isn't a great choice. In many terminals, holding shift prevents mouse input from going to the running program, and instead allows you to use the terminal's text selection functionality.
The problem is that the Sun is significantly brighter now than it used to be back then, so the amount of heating from the same amount of methane/co2 is proportionally more now too
There's nothing that forces a Wayland compositor to be written in C. I've seen ones written in C++, Zig, and Rust, but you could really use any language as long as you can still call the appropriate system/kernel APIs
You can easily hit a similar problem in other languages too. For example, in Rust, std::fs::File isn't buffered, so reading single bytes from it will also be rather slow.
Presumably, the AI would have access to just do all the git and web server stuff for you.. The bigger problem I see would be if the AI just refuses to give you what you ask for.
You could still offer the mocked APIs, but have them be opt-in. Also, having the compiler throw an error doesn't mean that an older, already compiled executable won't work.
As far as alternatives to what the article suggested go, I think the ideal solution would be to have a compile-time error, so the developers never even get as far as having their printing code try to run on the Xbox. And since it's a compile-time error, there doesn't need to be any kind of runtime error handling or cost either.
Not every program that's written will even be multithreaded, and there's a significant cost to using atomic operations when you don't need them. What is the disadvantage of having non-atomic Rc be available?