Manjaro 2.0 Synopsis This document covers the organizational, technical, management, and other changes we (the Manjaro Team, et al) like to see applied to the Manjaro Project. The goal of this document is to serve as a point of discussion, and ultimately, once a consensus on its contents and written goals has been reached, as a guide for the organizational restructuring of the Manjaro Project. Motivation The Manjaro Project has been declining over the past decade. It managed to sustain a sizabl...
CentOS and the way it was killed, managed by same team that manages Fedora, alongside the rest of Red Hat drama. Outside of Fedora, Canonical has made numerous breaking changes to Ubuntu, most notably by pushing snap down users’ throats and rolling out Ubuntu Pro, putting not only extended updates, but also vital security features behind a paywall. Part of the reason I opted for Tumbleweed is because SUSE is least prone to such acts - but it’s still a questionable arrangement in the long run.
All in all, I agree to disagree. We may just conclude that you personally have no reason to prefer Manjaro, especially since you had to manage it for others (which is not something I face), and that’s fine. I only interjected because you are very generous at extending your preferences and understanding on others.
I like to have Manjaro as an option. And I don’t mind Nobara, Bazzite or something else entirely - they have their userbase, and I’m happy the latter works for your needs.
CentOS has nothing to do with that and existed no more or less at the whims of its company than any other distro run by a specific group of maintainers, if the manjaro corp failed the exact same thing would happen to it.