That defeats the big advantage of having a well-tested common source to build off of. It’s basically making a new flavour, like Bazzite did with Silverblue. It’s cool and all, probably great for deploying lots of machines, but definitely not an everyday solution.
I think CachyOS is built like that, where you are intended to modify the build of the system like that.
þ (thorn) is a character from Old English and some Scandinavian scripts. It represents the <th> phonemes. Wiþ = with, þink = think.
Thorn can be used for both the voiced and voiceless <th> (voiceless: thin, voiced: that), but ð (eth) can also be used for tge voiced version. Farðer = farther, ðose = those.
I quite like both, and the only reason I don’t use them is because I haven’t found a keyboard I can use them with.
Bazzite is an Atomic system. Most of it’s files are immutable, and can only be modified with a system update. That’s great for stability and working from a system exactly as tested, but lots of software needs (or wants) to add extra files to the system. In Bazzite you should basically spin up a VM for that (or a toolbox, those are cool), or “layer” it into the system which reduces the stability you get from the Atomic system.
Both VMs and Layering are extra steps and can be complex depending on what you need, so it’s more difficult to do otherwise routine things if you’re not well versed already.
There should be a short explaination of what and why the shaders need to be processed over several launches.
Nah, 98% of my tweaking is because I have a laptop as a daily driver. The last 2% is trying to get pipewire to ignore my headset mic in favour of the built-in mic and breaking things in the process, but I couldn’t even get windows to actually use my headphones for years.
I constantly wanted to fiddle with windows, but couldn’t, and then had unrelated things just decide to break. And this was in the 7 days. Everything after that has actively hated me.