Having everyone have to discover the pro/con's of every system themselves, in the dark, with no social media / blogging around it, seems like a very strange position to me.

Technology should be highly social. Especially open source! It in unique-for-technology ways gives us something real to be social over. We can share and unfold and unpack.

This isn't entirely what you are talking about but Architectures of Open Source is still one of the best "what is this" explorations of the tech world out there. I think good advocacy has a lot of these elements (if not so total) in it. In ways that can show the bigger pictures, which AOSA at it's best does! https://aosabook.org/en/

The drift, the gap between the advanced guard of seasoned enjoyers and the rest of the world that doesn't know what their missing feels like material that deserves coverage to me?

Just stay heads down and keep doing the world, don't share, dont socialize has been the plan so far in a lot of open source. And I think the outcomes would be better if we tried methodologies other than this. Freaking weird that this is just accepted.

And it's crap. It still lists blog posts from 2012.

There is NO good overall diagram of all the moving pieces in systemd.

As someone that tried systemd init early on, without bias (I have no emotional attachment to how things start on my computer), it was incredibly clear that they would win.

Is your Civilization victory a Science, Military or Cultural one? I think that depends on how and if the technology is socialized and spoken of.

If people feel like it's an oppressor, something they don't understand that has rolled in, and now defacto is (is shipped in every distribution of note): it feels like a Military victory. Over them. It sparks no joy.

Appealing to the nerds can be a strong science victory. Preach all your amazingness. I personally can go on and on and on about how awesome it is that systemd offers workload isolation, least privileges, cgroups for juggling priorities. I love that mdns kind of just works for me, and integrates well with my resolver. There's little science-y reasons.

But there lurk Two Cultures problems everywhere. And figuring out how to bridge the technical to the world, how to sing praises, how to get the world to be interested in relating to, engaging in, giving it the ability to share in some of your wonder and awe: that is what turns Science Victory into a Cultural Victory. And it's what good worthy interesting projects deserve. And it should be an act we do, and help build. We should make appeals to the world, try to get them interested in relating to the upsides, and the downsides to, to give them something worth engaging. I feel like the negative creeps have absolutely slammed their way to Two Cultures wins, to appealing to the world with negativity, and I think some more deliberate, caring, thoughtful work and blogging would make a huge difference in building cultural momentum, in sealing in what ought be a Cultural Victory. That those who know systemd reasonably well largley agree with already, but that many people do not see or understand.

(Am I missing other victory types?)

Sure. These sites are fine rallying points, absolutely.

But they are also very old, and there's very few efforts I've seen to pitch and promote systemd. It's found and enjoyed by a lot of people (particularly those who had to deal with the tangled haphazard sprawl of cobbled together systems from the before times), it makes nicely visible what is happening on the system, integrates cgroups and good least capabilities practices.

But it feels to me like there ought be more ongoing and vocal celebration of this, enjoyment of this. More rallying points that trumpet the wins, that page people in to how nicely this helps. I want to see more positive tech advocacy, is what I'm saying. This is a fine site, yes, with lots of discussion. I've enjoyed decades of Lennart blog posts too. But I wish there was more. I wish this submission was a blog post of the same title. A fresh take, a fresh spin, on such a worthy-of-treatment topic.