the thing you must understand now is that regardless of their stated views, liars like Bryan Lunduke, Lennart Poettering, and Dylan M Taylor have demonstrated by their actions that they all have the same goal: a fascist software ecosystem that operates against our interests and exploits but does not empower our labor. it is the destruction of FOSS as we know it.

1/

Bryan Lunduke has always treated FOSS like a right-wing political project. he has also always misrepresented his goals as technical ones. the current moment is very convenient for him: he is using the valid need for an alternative to systemd to funnel people into fascist-controlled software ecosystems like Devuan and Artix. under no circumstances will Lunduke ever acknowledge the many init alternatives and distributions run by marginalized leftists. this is the game he has played for years.

2/

systemd has always been a lever of power; there’s no other reason to create an ecosystem of its shape. the person who grasps that lever is Lennart Poettering, and it always has been. I don’t need to write much on this; I watched the “oh shit” moment last week when systemd started accepting slop code, and again when an age verification mechanism was imposed on every systemd user and distro on Poettering’s final word. this was always the social structure on offer, enforced by a rigid ecosystem.
3/
@zzt When we used to shout this off the rooftops, people were all, "no no, see, it's *progress*! there are Good Reasons(tm)!"
@felix @zzt I was one of those, I'm afraid to say. Now rapidly reconsidering my positions and wondering if I'm too old to learn a BSD :(
@srtcd424 @felix @zzt never too old to learn a BSD!
Arguably easier to understand than Linux to be honest
@paul @srtcd424 @felix @zzt
BSD and Gnu/Linux are both re-implementations of the Unix later POSIX interfaces, and BSD and GNU have cross-fertilized over the decades, so there's less re-learning than one might expect.
Seriously considering going home to *BSD ...
@BRicker Sure, using them is pretty much the same, barring available command flags and stuff like that. Sysadmin work, not so much. Okay, it can be learned. The BSDs are famous for their documentation. I played with them. Saw what it involves. Definitely doable in a pinch. Still not a switch to make casually.

@felix
right.
OTOH if one is picking next one's next distro for avoiding the SystemD universal attack-surface, one is opting into sysadmin differences from mainstream already.

(Having started on PWB before BSD 3&4, and suffering thru multiple Gnu version churns, I alas expect flags to vary unexpectedly.)

(We had a client last decade that used *BSD for prod nodes (security out of the box) and CENTOS for internal dev nodes & desktops. Their problems weren't sysadmin.)

@BRicker I started using Linux a quarter century ago. SysVInit was *the* init system. It's systemd I could never get used to.

Can you please accept that I do in fact have a clue about all this stuff?

@felix so you weren't there when Sys V & SysVinit were new?
You have longish history with Linux but not Bell Unix, Sys iii, old BSD, modern *bsd, commercial Unix?
I'll acknowledge you've got a clue, but just the one. Some of us remember how BSD variants were incorporated back into SVR2, and the chaos that reined before that.

I think we're in agreement about (un)desirability of the SystemD Universal Attack Surface, so I'm not sure why you feel the need to argue with me.

@BRicker Perhaps because you jumped into my replies unprompted.