Gab vorher kein Firefox Maskottchen. Es gibt mehr oder weniger noch ein Mozilla Maskottchen mit dem ursprünglichen Dino-Logo, falls du das im Kopf hast:

It’s right-wing trolling that it’s specifically non-binary. It’s just iconography they use throughout Firefox, when displaying error messages or the like.

Oh man, you keep finding these hex values in other places. I assumed the author of this particular theme just made them up, based on what they thought looked good.

And yeah, that is wild to me, that it passes a contrast check. I’m far from having the worst eyesight and still find it needlessly difficult to read.

Yeah, I do customize the themes like that, too, usually also #ffffff for the foreground or vice versa. It would just be nice to not need to maintain my own themes. 🥴

I try to kick my circadian rhythm with ample light, so for that I switch between light and dark theme more or less around sunrise/sunset. Staring into a bright screen with light theme isn’t as bright as being outside, but then I can at least also turn on all kinds of lights or sit outside somewhere, without it being as detrimental to readability as it would be with a dark theme.

I guess, what really bothers me here in particular is the extra low contrast. The background does actually use the correct color, that you point out. But the foreground/text color is #654735. That’s brown:

I don’t know where that color comes from. None of the original Gruvbox colors are that. It is dubbed as a “Gruvbox Material” theme. I do have opinions about the new Material You styles having shit contrast. But I don’t believe, it’s supposed to be quite as terrible either.

And well, yeah, I do usually end up modifying the Gruvbox themes to just set background to #ffffff, foreground to #000000, or vice versa for dark themes. It does work quite well IMHO, which is what makes it all the more frustrating that so many Gruvbox-like themes choose to go the other way.

As far as I’m aware, it started out with a Vim color scheme, which looks like this:

https://github.com/morhetz/gruvbox

And yeah, that’s just become a really popular theme, which got ported to virtually anything that can be themed.
Personally, I really like the color palette, but not that so many takes on it have text that’s horrendously difficult to read…

It’s Apple’s programming language, kind of intended as a successor to Objective-C.

From what I hear, it’s actually decently designed and has quite a few similarities to Rust. Still not sure, how great it is outside of the Apple ecosystem…

My instance went down, so I’m way too late to make this joke, but anyways:

We’re not cantankerous, just a little …crabby. 🙃

Considering their policy for the majority of their existence has been that open-source is cancer, it might as well be viewed like that. Just buy the central open-source exchange platform and slowly make it worse to hurt all of open-source.

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…

It’s key-based client authentication. Just open your SSH key’s .pub file in Microsoft Publisher, then export to PDF.

RIP

In my experience, the biggest problem is that maintainable code necessarily requires extending/adapting existing structures rather than just slapping a feature onto the side.

And if we’re not just talking boilerplate, then this necessarily requires understanding the existing logic, which problems it solves, and how you can mold it to continue to solve those problems, while also solving the new problem.

For that, you can’t just review the code afterwards. You have to do the understanding yourself.
And once you have a clear understanding, it’s likely that the actual code change is rather trivial. At least more trivial than trying to convey your precise understanding to an LLM/intern/etc…

Yeah, IPv4 addresses use four bytes. Those four bytes are represented as four decimal numbers, separated by dots. And a byte can only represent the decimal values 0–255.

Everything I implement at work is open source because I don’t want to wait for a purchase approval.

Just to say, though, I feel like 99% of the software we deploy is open-source for that exact reason. Projects generally start out small, where you try to evaluate some concept. You’re not gonna spend months to go through the purchase process of some proprietary tool, if you can help it…

Don’t forget SuperTux! It got a larger update just a few days ago.

https://www.supertux.org/news/2026/03/14/0.7.0

So, uh, if you’re already using jq, this should also format JSON:

echo "{\"key\":\"value\"}" | jq

😅