We’re pretty public and transparent about everything we do, ask away!
Please read all the way through before responding. Thank you.
Best read during perhaps the morning, with a coffee, and some time on hand to ponder and consider things.
Our shtick is kind of “you don’t have to worry about any of this anymore because it’s not important to you, it’s just handled.”, or as someone mentioned (Paraphrasing) “it’s for people who are at the End Game of their days wanting to do things on their own and would rather someone do it for them”
The more you attempt to provide everything and cater to the whims of all, the less you will find you are able to do so, the greater the burden upon everyone; the health of the project, it’s longevity and capacity for persisting beyond the point of it’s directed and active support, is massively impacted. Cater to people at their EndGame and the service you provide will certainly find it’s EOL someday.
The appeal towards providing software for people that “just want it to work” or more specifically “don’t want to deal with the hassle of anything at all ever” is a false preconceived notion drempt up by some business shmo working a deskjob trying to write the next 5 articles his/her company mandated even if it produces little to no meaningful content. The point is, it doesn’t exist because no one wants you to do that, but there are certainly people who want you to think they do. 99.99% of people would very much prefer to be able to maintain their own Linux Installation with ease without the over-reaching dictation of a linux overlord who spends the majority of their time designing ways to remove the right of choice from them and others due to some belief that they don’t have what it takes to do it themselves…no amount of hand holding, education reform administrated by you, is going to. The key here is to notice the direction of the goal is not at fault…the problem area is the approach with regards to implementation. Don’t focus on Educating anyone, educate yourselves and stick to what you do well, which is providing what you want to see bazzite become based off what it means to you in consideration of others, not the other way around…if you do it well, it will attract others (as it has already to some extent), if you continue to do it well people will stick around longer. People are free to choose when and how they want to learn. It’s not something you are required to or expected to shovel into the heads of every passing individual you believe doesn’t understand what you think they need to.
Instead of documentation detailing what X, Y, Z feature is and why it’s there, document practical, appropriate, instructional and genuine end-user use case examples such as snippets of various scripts, configuration location lists, and step by step bullet points for a subset of what you’ve allowed the end user to do, which will be everything they wish to do, such as build and compile a source version of hyprland and supplement the script configuration gamemode uses with sddm to launch kde plasma with hyprlands launch instead…for instance (please and thank you).
As a user of many Linux distributions for both X86 and Arm Architectures I’ve been puzzled by the growing propensity for people’s beliefs to sway more towards what could be regarded as an Easy Approach to maintaining a distro by incorporating software which is easily accessible, widely available, and largely much more thoroughly documented, if only by right of having less exposure of less profitable/business attractive options that are more inline with end users views of what’s useful instead of what goes beyond the point of acceptable/necessary.
Those projects which respect users go largely ignored or disregarded as they don’t provide (initially anyway (usually)) the norm of business attractive features like remote access, cloud deployment, or for which the glorification engine of the industries hypers (marketing people?) are not present in order to “Talk it up to Daddy” to get people interested by publishing videos, blogs, or more meaning…ful…quora articles about. There are problems with this however and it stems from the preconception relating to maintainer responsibilities within the scope of expectations provided by the user base for which the Distribution aims to cater towards. That is to say, it is not a long term viable solution for many end users, to simply have everything administrative/root related taken care of for them by strangers on the internet. Having the freedom to access, change, modify, add, remove, or modify any aspect of the user experience by the user, is the first priority as an end user such as myself, when picking a distribution.
I’ve been trying bazzite for the past several months after purchasing my Lenovo Legion Go and wanting to never have to rely upon another Windows installation again, Bazzite Linux caught my attention as it was aimed at providing a Functional and Readily Accessable means for Linux Gaming without a keyboard/mouse and using gamepads.
I was excited at first, and for the most part I’ve been enjoying my time in using bazzite. However, with the standard init system among mainstream linux distros adhering strictly to an overbloated, end-user unfriendly/technically overcomplicated, force fed adoption of SystemD…marked the beginning of my trail of discontent when it comes to my current experiences involving my use of Bazzite as a Daily Driver.
SystemD
No Clear or Primary Package Management Utility or pkg distribution channel aside from flatpak and rpm-ostree.
rpm-ostree, in my experience makes it down right impossible to remove a package provided in the default installation (maintainer packages?). override remove simply made things inactive, despite my attempting to uninstall/override remove them.
The usage of containers is not, imho, a viable alternative solution if the goal is to simply compartmentalize the exposure of risky system interactions which could render the system unfunctional.
It Takes control away from the device owner, and fails to provide what is regarded as it’s core feature (the one for which the lack of control is purported to solve), continued functional operation in the event of a complete system breakage (Software Bricking events).
I believe that the more correct approach would be to provide a minimalist system, with the freedom to selectively pick and choose the core packages by the end user and let them decide when and what they would like to choose. This is strongly reinforced by the fact that over the months I’ve had my installation already set up, but upon update, I would find application packages I had either previously removed/uninstalled, reintroduced (unattended stylez) to the system again and again…One of the changes most recently was the desktop application launcher for returning to game mode…How is this even a thing stilll…you know all you need to do to go back to gamemode is to, log, out…Every time I booted the system, went from gamemode to desktop back to gamemode and back to desktop, despite deleting the desktop icon for the launcher, it would somehow magically reinvent itself upon my screen the next time…furious
but whatever is causing that to happen resides in /usr…can I change it or fix it without putting more stress and pressure upon the maintainers to cater to my every whim while I’m getting things setup the way I want it?..no…I feel like I could post and post and post and post to people who may or may not read and if they do they may or may not have the time necessary to assist me.
You could have chosen, Runit, or S6 for init and hand-crafted if required, the service scripts that coincide with the packages required to provide the same end user gaming experience.
You could have chosen a virtualization solution such as KVM/QEMU rather than relying exclusively upon LXC’s
You could have allowed for the modification of desktop environments to allow for people to pick and choose between ANY and all desktop environments available (made impossible due to RO /usr, and maintainer enforced core packages, coupled with the lack of cohesion between the various pkg distribution channels). This includes Enlightenment Desktop, Budgie Desktop, Sway Desktop, Hyprland (which is the one I was wanting to play around with), or whatever else.
Modifiable is fine and great, modularity does not it equate strokes his beard
Also…on a somewhat related note.
Someone Please Help !!!
you bring up a lot of points. I think it makes most sense to address the general theme that I can make out from your post: Customization.
I think you are trying to swim against the current. Yes, Linux distributions (immutable or not) can be very opinionated. Some are more hands-on and some are more hands-off. If what you want from a Linux system is not provided by a given distribution or spin, then I advise you to look for some alternative, of which there are plenty.
For me, Bluefin was quite a big change and I had to rethink how I use my new system. This change was also exciting though 
. If you want to stick with an immutable Linux system, I recommend to take the time and to embrace how things are done differently, so that you can swim with the current instead of fighting it.
1 Like
See this is the thing. Your busy telling me how things are, and how I am not in alignment with those things. Who is it that distributions are trying to provide working systems for, their users, or their maintainers sensibilities?. It is rather typical for the well educated and much more superior “dev” to point out how the user clearly doesn’t know what they should expect and if they don’t like it to GTFO to another distro. No respect, that’s why you get none in return.
If this represents the maintainers and bazzite developers mindset then I’d be glad to gtfo. Let your project get buried in time and forgotten along with the rest of the shoulder shrugging brigade.
Who know’s, maybe AI can replace your userbase once you’ve sent them elsewhere, wouldn’t that be nice?. Have a pleasant day.
Your post is clearly not in good faith, Universal Blue isn’t for you.
4 Likes
No Bazzite developers replied to you in this thread, I am the first.
I am not interested in making a meme distro for you.