@alcinnz On my side I think it's a bit weird to just put it into just "bro". I think a term that is too vague helps no one because it's quite difficult to meaningfully use/adopt it in existing communities and have it understood by people being criticized, I think it ought to be split in smaller chunks, or even just leaving it at words like ableism/entitlement/…
Also while I think it makes sense, at a face value, the descriptions are a bit weird, like the "hiding configuration options" part isn't as simple as a lot of undocumented options are useful for basic needs like accessibility (things like an expert mode being of course a reasonable way to not hide but filter options), and I think it helps no one because then users will try to share unofficial documentation, occasionally leaving them with broken setups because they can't know what the option actually does.
And I think a lot of software is both community-hostile and fork-hostile, meaning that creating a fork or a full-on replacement is a real pain (technical, social, material/infrastructure, sometimes legal, …) but it's sadly often the only way to address actual needs (needs ≠ wishes), which a single project cannot address but a cooperative community of different projects should be reasonably able to.
Ironically I would say that you're contradicting yourself here:
> You can still have your Linux distros which don’t use systemd, or are none of you techie enough to assemble one?
In a way, because I can't point for sure at a beginner-friendly distro that is community-based rather than one where the important decisions are only made by the leader/board, telling "leave if you don't like it" like what happens with Ubuntu pretty regularly.
systemd's reach of course having a lot of user-facing consequences because of either bugs on itself like mishandling fstab and leaving the system hanging, or design decisions breaking other programs like how closing programs on session leave broke switching of users at the lockscreen.
And forking/creating a distro to replace a core dependency is pretty high in terms of pain, a lot being irrelevant to technical knowledge. (need to build a community, you need infrastructure and so money, and maybe being prepared for some legal troubles given some awful trademark policies like Rust and Mozilla's)
