I’m a little too chalant.

Third. I swear by them (and got their keyboard too, in Family Basic colors, and mouse in NES colors).
The moment they put out a keyboard in Atomic Purple, I’m throwing a bunch more money at them.

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

No it certainly is not.

The meaning is different if it’s pointing the other way

A little on the nose, isn’t it?

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.

Hast thou considered: while holding an item, hold up on the D-pad, then release B, then jump up in front of a climbable surface like a vine or a fence and hold B in time to catch the item. Now you’re climbing with the item.

Actually it’s Kitsune Tails.

Sorry, that’s not correct. SMB3 was released in 1988 in Japan. It was delayed in North America until 1990 and released in the same year as SMW, while Nintendo of America ironed out its Super Nintendo console launch.
Super Mario World, in fact, started development as a port of Super Mario Bros. 3.

A lot of people did, it’s a pretty important work culturally

I’ve been using this, it’s great! Thank you.

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

I mean DARE was right up there.

CAT. K A T. I’m outta here.
(I know there’s two Ts)

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.