This is awesome work, I’m happy to see systemd on musl getting more attention. Poor Khem was doing it all by himself for years.

Baby Mammoth - Another Day at the Orifice

Gotta have blue hair

San Diego

I don’t know if this is still the case, but IIRC browsers (chrome and Firefox) have their own sandboxing which is quite effective, but their efficacy is hindered by flatpak.

Early Knoppix live CDs have a special place in my heart

I’ve used silverblue on my gaming rig for over three years now. It has been a completely uneventful experience, so I really like it.

The only pain point I have is that compiling kernel modules is an utter disaster and it’s ridiculous that there is not a seamless mechanism for this yet. Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.

C++ is way ahead of C in the same way that a metastasized cancer is way ahead of a benign tumor

Was this written by AI?

Linux has dominated the router firmware market for a loooong time. Nearly all vendor firmware for consumer routers is Linux based.

But but there is no ethical consumption under capitalism so that means I shouldn’t even try

Ligatures 🤢🤮🤮

Reminder to read the official git book. It’s free and it’s useful. My dudes, stop pretending to understand your tools and actually learn them.

This is amazing

Our current understanding having spoken to systemd developers is that we should be able to find a path that brings us much closer to upstream, if not entirely.

The only way the systemd developers will allow musl support upstream is if musl supports the glibc-isms that systemd uses.

They have been extremely clear that they will not carry patches for other libcs.

Lol

I find GNOME’s “must be perfect” approach to accepting new code counterintuitive.

One of the largest benefits of having a clean architecture is increased velocity and extensibility. What’s the point in nitpicking over perfection when it takes literally years to merge a feature, arguably one considered basic and essential by today’s standards?

KDE is on the other side of this pendulum, integrating everything and resulting in a disjointed, buggy disaster.

Where’s the middle way? It used to be XFCE. What is it now?

This makes no sense because dbus uses unix domain sockets.

It sounds like you don’t actually understand what dbus is.

“Bro just use sockets lol” completely misses the point. When you decide you want message based IPC, you need to then design and implement:

• Message formatting
• Service addressing
• Data marshalling
• Subscriptions and publishing
• Method calling, marshalling of arguments and responses
• Broadcast and 1:1 messaging

And before you know it you’ve reimplemented dbus, but your solution is undocumented, full of bugs, has no library, no introspection, no debugging tools, can only be used from one language, and in general is most likely pure and complete garbage.

Memory bugs are only a tiny share of the foot guns in C++

This is basically C++ in the embedded world, and yes it’s the only good C++