

Ooh, I’ll try that, thank you


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.


I switched to Arch full-time recently and I’ve got to say, it’s way more accessible than its impression suggests. It just… works. The installer is about as easy as any installer these days. There have been no major breakages, even due to my own stupid mistakes. There was the one linux-firmware package thing but that was really just a minor speed bump and the instructions were easy to follow.
Do not touch.
Once, I felt a vague itch on the front of my left shin. I rubbed the back of my right shin on it. I had a very itchy rash on both for several days.


That dang masculine -er


That’s a lot of very interesting assumptions you’ve made about me, friend.


I’m gonna keep using the word “sideloading” because it is a perfectly legitimate act and I refuse to let them redefine it to demonize us.
I’m not sure why you’re helping them.


Absolutely agree.


Well, they’re technically correct (likely by accident). It is no longer a diagnosis that is used.
Reminds me of those 90s Harmon Kardon PC speakers


Time for my TRIsexual awakeningoh people already say that, they say “trYsexual as in I’ll try anything”, now it’s just gross


This isn’t quite in line with your question but it’s adjacently meta:
the first time you fall to your death in Bastion the (amazing) narrator says “…and then he fell to his death. … Ahh, I’m just foolin’.” and then you respawn on the platform because videogame.
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.