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.
Yeah I realize that. My go-to comparison would be PDF. Where Firefox has PDF.js (I think?), Chromium just… implements basically seemingly the entire (exhaustive!) standard.
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…)
Nature
Ever visit a zoo and notice any smells, e.g. in the ape house? That’s a part of nature, of course.
It’s just we’re trying to avoid that.
No kitty graphics protocol? 🤨😔
To you, @toothpaste_ostrich@feddit.nl, and anyone else planning to do the switch:
Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named product.json which allows you to “regain” access if you populate it with the following values:
{
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"itemUrl": "https://marketplace.visualstudio.com/items",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"controlUrl": ""
}
}
(Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in ~/Library/Application Support/VSCodium.)
*If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.
To be honest, I think I prefer the Emacs one due to how absurd it is: https://youtu.be/urcL86UpqZc
But all of them are hilarious.