I'm a glossy person as well, but I believe the Steam Deck OLED also has a glossy display. Valve does add anti-glare texturing to the glass, though, but it doesn't diminish the appearance for me.
(Disclaimer - I just have the anti-glare LCD, not the OLED.)
I mean, sysvinit was just a bunch of root-executed bash scripts. I'm not sure if systemd is really much worse.
Systemd was created to allow parallel initialization, which other init systems lacked. If you want proof that one processor core is slower than one + n, you don't need to compare init systems to do that.
Correction: migrated to GitLab, but I don't expect they'll want to keep it there.
The Nuzu repository is already wiped.
I already left the Messages app after the Shortcut Bar annoyance. This would have been another death knell to me that the app is past its prime.
My workaround for this is to create a Steam shortcut to a browser, and you can launch it while running a game.
Steam even provides a list to all running applications that it launches - not just the most recent one.
With UI decisions like the shortcut bar, they really don't. I switched to another SMS app because I couldn't stand it.
I've been disappointed in general with the XPS line in recent years. Dell has made some keyboard changes that I am not a fan of:
I've been purchasing the XPS line of laptops since 2013, but I stopped as soon as those changes landed and the Developer Edition of their laptops shipped with inferior hardware compared to the Windows ones.
On Android, it moved SMS messages from the shared SMS store upon receipt and to Signal's own database, which was more secure.
I tried to take hourly snapshots of an already-large Minecraft world using Git, but after a few years of snapshots, the repository became corrupted.
One of the issues was that regardless of any player-based changes that occurred, the spawn regions were always different as they were always loaded in memory.
I'm not familiar with creating fonts specifically, but you'll want to commit any resources necessary to recreate the font file, including any build scripts to help ease the process and instructions specifying compatible versions of tooling (FontForge in this case). Don't include FontForge in the repository, of course.
The compiled font files should be under releases in GitHub for the repository.
Git isn't generally meant for binary resources but as long as they're not too large, they'll be fine. You just may not have meaningful ways to compare changes easily.