The funny part is that upon reading your question, I figured surely the Wikipedia page would have that information. Then I saw that it said in the first few words:

Xbox (stylized as XBOX)^{[[2]](https://www.theverge.com/news/931918/microsoft-xbox-rebrand-caps)}

…which links back to the same article. Which is how I found out that the article answers your question. 🙃

The use of all caps for Xbox is a return to original form, though. Microsoft’s first Xbox logo for its console was all caps, and the company has favored using similar capped versions for the Xbox 360, Xbox One, and Xbox Series X / S console logos.

They have a contact e-mail address at hello [at] fossify.org.

Apparently, that’s American English. And for whatever reason, it’s the British that are less hoity toity about it:

• “brackets” or round brackets ( )
• square brackets [ ]
• curly brackets { }

https://en.wikipedia.org/wiki/Bracket

Yeah, differentiating between multiplications vs. divisions and additions vs. subtractions doesn’t make sense, because they’re the same thing respectively, just written differently.

When you divide by 3, you can also multiply by ⅓.
When you subtract 7, you can also add -7.

There is one quirk to be aware of, though. When people notate a division with a long horizontal line, that implies parentheses around both of the expressions, top and bottom.

It certainly does!

…but, uh, well, it’s a widely-spaced monospace font in this case. That’s the one situation where kerning actually cannot matter.

Which seems intentional. I believe, the cartoonist is being more clever here and referencing a common ligature, specifically the first of these two:

https://en.wikipedia.org/wiki/Ligature_(writing)

Presumably the two letters got written together so often in this futuristic universe, that “fi” has actually become its own letter. Like how in German the “ß” came to be from a ligature of a long S (ſ) and a Z (which was written as ʒ), so together “ſʒ”.

Maybe someone who’s deep into Simpsons lore can confirm that theory. 😅

Pʀᴏʀᴛ

It’s a mockup I found on image search (from searching “neobrutalism GUI” or the like): https://www.magnific.com/premium-vector/hand-drawn-neo-brutalism-ui-elements-collection_186004756.htm

And yeah, that theme you linked is already pretty cool. Not terribly enamored with the retro aesthetic personally (especially with bad contrast like here), but if that can be done with KDE/Kvantum, then an actual neobrutalist theme, or just one with the papercuts fixed, is likely just as possible…

Well, this kind of design language is actually referred to as “neobrutalism”, so you might find a theme under this name. But from what I’ve seen so far, it’s mostly a thing in web design at this point…

I also always find the minimalism vs. maximalism debate interesting for usability. Lots of minimal designs are so flat that you can’t tell a button from a label or icon.
At the same time, iOS’ new Frutiger theme regularly confuses me with its transparency, e.g. yesterday I saw that the silent-mode notification had a ➋ inside. It was centered and everything. Then the notification went away, but the ➋ stayed, because it was from an app icon behind.

I wish, we could throw out the bad eye candy, like transparency, while keeping the good parts, like 3D buttons and such. I feel like this kind of neo-brutalist UI design isn’t the worst direction to go in:

(This particular example isn’t perfect, like the buttons are flat, while there’s useless shadows around the boxes. But yeah, could just move those shadows to the buttons and it would still look fine.)

Servo company? It’s an open-source project underneath the Linux Foundation. The Servo Shell source code seems to be here: https://github.com/servo/servo/tree/main/ports/servoshell
It probably wouldn’t be too difficult to compile it yourself, if you really want it.

However, you have to mind that it’s damn near impossible to build a browser from scratch that supports the majority of web standards at this point. Servo does not do so. Most webpages will not be usable on it.
That’s the reason why they don’t care to provide a general-purpose browser interface. Because Servo is only useful at this point when only a specific webpage or specific set of webpages needs to be displayed.
So, generally when it’s embedded into hardware or into a software application, where the user does not have a URL bar to type arbitrary addresses into, and where the webpage to display can be specifically crafted for Servo.

I’m not much of a fan of Debian, but in your position would still recommend it. You’ll have enough to learn about from just using it as a server. You can learn about potential advantages of other distros later…

I’ve been wondering, if you could combine LLMs with a logic programming language like Prolog. The latter is actually able to reason through things, you “just” have to express them in Prolog facts and rules.

Well, from doing a quick online search, I’m most certainly not the first person to think of this, which does not surprise me at all…

Yeah, I can understand the frustration when an external decision forces you to disappoint some of your users, but ultimately you have to pick your battles. When neither the Python nor Rust ecosystem thinks those platforms are worth supporting, it’s probably not either worth it for you to worry…

The problem is that in this case, the LLM just naively auto-completes a password from what it knows a password to most likely look like.

It is possible to enable an LLM to call external tools and to provide it with instructions, so that it’s likely to auto-complete the tool call instead. Then you could have it call a tool to generate a correct horse battery staple, or a completely random password by e.g. calling the pwgen command on Linux.

But yeah, that just isn’t what this article is about. It’s specifically about cases where an LLM is used without tool calls and therefore naively auto-completes the most likely password-like string.

I imagine, it’s a matter of asking it to generate some configuration and one of the fields in that configuration is for a password, so the LLM just auto-completes what a password is most likely to look like.

Yeah, and the worst part is that submitting the PR is trivial. You just offload the reviewing work onto the maintainer and then feed the review comments back into the AI. Effectively, you’re making the maintainer talk to the AI, by going through you as a middleman, a.k.a. completely wasting their time.

If you’ve got access to a microwave, I’ve found rice dishes quite convenient, like for example a lentil curry. They generally re-heat without tasting worse and the rice traps the moisture, so even if your container isn’t 100% sealed, you’re unlikely to get mess everywhere.

(Though I’d still recommend getting a properly sealed container. Personally, I also transport my food in a separate cloth bag, so that if it should ever leak, I can just wash that bag.)

I always thought openSUSE’s package manager zypper has quite a few neat ideas:

• It offers two-letter shorthands for subcommands, so zypper install→ zypper in, update → up, remove → rm.
• When it lists what packages it will install or remove, it will list them with the first letter highlighted in a different color, kind of like so: fish git texlive
  This makes it really easy to visually scan the package list, and since it’s sorted alphabetically, it also makes it easier to find a particular package you might be looking for.
  And while there’s separate lists for packages to be added vs. updated vs. removed, they also color those letters in green vs. yellow vs. red, so you can immediately see what’s what.
• When it lists items (other than packages), it prints an ID number, too.
  So, zypper repos gives you a list of your repositories, numberered 1, 2, 3 etc., and then if you want to remove a repo, you can run zypper removerepo 3.
• When you run a zypper search, it prints the results in a nicely formatted table.

Documentation: https://doc.opensuse.org/documentation/tumbleweed/zypper/

Hmm, I don’t know about Pacman, but for example openSUSE’s zypper remove has a --clean-deps flag, which doesn’t exist on the other subcommands. So, it wouldn’t make sense to have it be zypper --remove --clean-deps…