They just reach into their computer case and tickle the pins on the CPU when they want to initialize PID 1.

leg

There’s a scene where a giant robot knight stabs the crap out of a giant ball that looks like the Epcot Center.
Mistreat your altar boys long enough, and this is what you get.

Fine
scended

“Welcome… to NIGHTvale.”

I just sed -i ‘s/bookworm/trixie/g’ /etc/apt/sources.list.d/*

Nothing against Peter Dinklage. But Natasha Lyonne really makes the show. I’m not interested in watching it without her.

Seems pretty clear to me

Trickery is not the best way to demonstrate your faith in your cause.

No it certainly is not.

Is there a premium on hyphens?

Yeah, fair. And 25.10 is a short-term release anyway. The point of it is to get a running start on 26.04.

They do have a habit of overcommitting to tools that are not yet ready.

To add a little: systemd is just a service manager. It manages services.

You can plug systemd-journald into it and now it does logging too. Or you can use rsyslog, or both together, or something else entirely.
You can treat your network connections like services (technically units) with systemd-networkd. Or you can use NetworkManager. Or both, or neither, etc.
You can treat mount points as units because somebody said “let’s define mounts in a new kind of unit file and have systemd initiate them as a service” or you could continue using fstab.
You could use systemd-resolved but you don’t have to. You could use systemd-udevd (you probably already do because most distros run it by default, though it still pulls from /etc/udev) but you don’t have to.
These are all optional extensions.

It turns out it’s really handy to have a robust service management backbone because you can plug any number of things into it, as long as you reimagine those things as services (again, technically units).

So what’s the controversy?
As far as I can tell, it boils down to “they shouldn’t have made systemd-networkd only be able to talk to systemd, they should have made it work with every possible init system”.
Which is understandable, but not really defensible.

Ooh, I’ll try that, thank you

Temmie went to git leg

It’s absolutely not. It tends to be bundled that way, but systemd does one thing. It does that one thing very well. There are many components that tie into it.
If you believe that defies the UNIX philosophy, then you must also believe that the kernel includes every aspect of a graphical desktop environment, just because the latter depends on the former.

It’s too good and people keep using it as a framework for their own tools and that’s bad for some reason

Debian closed that gap in Bookworm, where nonfree firmware was included in the install medium by default.

I’ve noticed sites are getting around Reader View by not loading all the content right off the bat. Just enough so you start to scroll so they can launch all the popups.
Means Reader mode only has a paragraph and a half to show.