FizzyOrange

Very good points. A codebase that gets this VERY wrong is Gitlab. I think it might be a dumb characteristic of Ruby programs, but they generate identifiers all over the place. I once had to literally give up following some code because I could not find what it was calling anywhere. Insanity.

Another point: don't use - in names. Eventually you'll have to write them down in a programming language, at which point you have to change the name. CSS made this mistake. foo-bar in CSS maps to fooBar in Javascript. Rust also made this mistake with crate names. A crate called foo-bar magically becomes foo_bar in Rust code.

You won't get very far in life with such primitive black and white thinking.

One annoying thing on Windows...

You could write a dozen rants about other similarly annoying things on Linux (or other ones on Windows).

Buying several OEM keys is still going to be cheaper than a retail one though.

It can understand, just not as well.

You can't confidently say that because nobody knows how to solve the bullshitting issue. It might end up being very similar to current LLMs.

He's right that it's probably harder for AI to understand. But wrong in every other way possible. Human understanding should trump AI, at least while they're as unreliable as they currently are.

Maybe one day AI will know how to not bullshit, and everyone will use it, and then we'll start writing documentation specifically for AI. But that's a long way off.

I wouldn't recommend it. I actually looked up COBOL jobs a while ago, and while they paid more, it was only like 20% more - not enough to make it worth it IMO.

Neat idea! I bet it's expensive though.

No, there's no proper equivalent to Ctrl-Alt-Del. It's a major flaw in the Linux desktop. You just have to hard-reboot.

Edit: Downvotes, but you won't get any suggestions that match Ctrl-Alt-Del. Only

• Ctrl-Alt-Fn - Disabled by default in lots of distros I think, and it doesn't have high priority so it's not guaranteed to respond like Ctrl-Alt-Del does.
• Magic SysRq - Zero UI, so you have to magically remember a load of random keys, and there's no way to kill the specific offending process.
• Ctrl-alt-backspace - Brute force, kills X (does it even work on Wayland?).

Prove me wrong. Ctrl-alt-delete will respond even when the system is overloaded, and it lets me interactively see a list of processes and kill one of them. Can you do that in Linux?

Linux is never going to solve this problem while they treat the UI as "just another process".

Yeah I tried Buildroot and Yocto and got frustrated. Buildroot did work, but it does a ton of stuff with a ton of not-very-well-documented options, and it definitely wasn't integrated into a proper build system. Like there's no way I'd trust any kind of incremental build.

I ended up doing it myself. Tbf I was just benchmarking kernel boots so I didn't need userspace or even real hardware. I only needed OpenSBI (a RISC-V firmware thing) and the kernel.

Frankly OpenSBI is a rather undocumented mess too. Incremental OpenSBI builds don't work, and I did try and contribute fixes but despite the repo being on GitHub they auto-close PRs and tell you to use git send email from the command line to a mailing list like it's the 90s. I shit you not. How to keep away contributors.

Anyway my conclusion is that the whole Linux OS building story is a shit show. If you only want a basic image with busybox etc. you can probably do it yourself and then you will actually understand it, but you will just be recreating Buildroot.

Huh I did not know Roku (the on-the-way-out TV company) made their own scripting language. How bizarre.