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…)

I only learned that this was a thing like literally two days ago!

Why does it compare against $1 for the string match? Wouldn’t kudasai be at the end of something like $*?

No kitty graphics protocol? 🤨😔

At this point, TOML is my favorite since it basically amounts to an attempt at standardizing the .ini/.conf style of config “language”/files. It’s still simple enough, but pretty powerful, and was seemingly good for the Rust and Python projects to be convinced to choose it as a default…

Server (Linux) and personal machine (non-Linux Macbook) with the same general shell config (aliases etc.), but different applications/CLI tools installed.

No idea how it compares against the Nix paradigms, but I like the ease of use in setting up a new machine. It’ll copy all files to their intended destinations and will be able to fill in credentials from templates using e.g. rbw (third-party Bitwarden, i.e. password manager, CLI tool), meaning, once all fields have been templated, you can make it public without even worrying about leaking a personal email address (I use different ones for git vs. other accounts vs. even other stuff).

Yeah, and then you start to configure any edge case, and then you’re basically already at the point where chezmoi would be useful. Lol, I’ve been there

Chezmoi my beloved

Competent terminal editors offer optional mouse support…

Soon… surely… any day now… not coping…

The “worst” part is it already works, just takes long to become as perfect as possible. See the showcases like filetree.webm.

Edit: track the broader discussions/progress at this wiki entry.

To you, @[email protected], 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.

Just install Mommy in Samuel L. Jackson mode