Helix is “it just works” but it actually does, without having to get lost in the (config) sauce.

It’ll be unstoppable once they finalize and ship the plugin system.

Edit: and I haven’t even mentioned the descriptions above commands, the command palette-like functionality in <Space-?>, nor the tutor yet. It’s just so much more beginner-friendly.

The Unix principle of piping between two or even multiple programs, together with “all data should be in the simplest common format possible” (that is, largely unformatted strings), was a really clever invention to be popularized. As proven by the fact it is still so useful decades later on a myriad of computers unimaginably more powerful than what they had back then.

It’s not perfect by any means (alternative title: why something like Nushell exists), but it’s pretty good all things considered I dare say.

No, you didn’t mention “than in the US,” so people assumed you were sharing an American perspective under an article about US states’ cost of living.

Greetings from your southern neighbor!

Thanks for these explanations, that makes a lot more sense now. I didn’t even think to consider browsers might be using something else than an off-the-shelf implementation for image/other file formats…, lol

Honest question, since I have no clue about web/browser engines other than being able to maybe name 4-5 of them (Ladybird, Servo, Webkit, Gecko, … shit, what was Chromium’s called again?):

What makes browsers/browser engines so difficult that they need millions upon millions of LOC?

Naively thinking, it’s “just” XML + CSS + JS, right? (Edit: and then the networking stack/hyperlinks)

So what am I missing? (Since I’m obviously either forgetting something and/or underestimating how difficult engines for the aforementioned three are to build…)

No kitty graphics protocol? 🤨😔