You must log in or register to comment.
This is unironically why I switched over to Bazzite, and why I recommend it to newbies as well.
I will tinker too much and break things.
At least with Bazzite, if I thinker too much in a container, I just throw out the container and try again.
(And if you insist on fucking up the core OS, presuming at least some of it is still intact, you can rollback/reinstall fairly easily)
Bazzite was too limiting for me and the layered updates made updating take forever. I was only using it on a media PC at the time too, so it wasn’t as if I had that many changes.
I’m perfectly happy with CachyOS. Can basically do whatever I want and snapshots are a nice safety net. Updates take like 2-5 minutes depending on how long it’s been since the last time I ran updates and the power of the system (Steamdeck always takes longer than my desktop or media PC).
Hey I mean, if Cachy works for you, that’s awesome!
I’ve not tried it yet myself, but I’m not gonna be like an insane hyper fan boy for Bazzite.
I will fully admit to just having had toooo many insane experiences trying to get Arch to do what I wanna do… kinda sucks to have to rely on the AUR for random dependencies for something like byilding a whole game engine from source.
But, my use case is not your use case, I’m geneuinely glad you’re happy with what works for you.
The con is more like:
You must configure something you never wanted to know anything about, but I guess today is a learning day…again…
must configure something you never wanted to know anything about, but I guess today is a learning day…again…
surprisingly, it’s not all that bothersome, We used to do it all the time on the glorious windows xp when the computer inevitably stopped running properly.
For a millenial Windows user, Arch and now Cachy of all distros are now on par with how win98, WinXP and Seven worked on personal PCs in the 00s. I baselessly assume that a lot of people of my generation, who fought with the blocky interface of these, would feel more at home there than on Win10/11.
Vibe coding nixos to combine kde and gnome on an ext2 raid with snapshots
I copy paste whatever the documentation tells me to do. Somebody wrote it for a reason.
“It’s so great that Linux actually gives me control of my OS. I wish all OSs respected their users like this. I’m gonna configure it to my exact specifications…annnd I broke everything.”
It’s not about knowing what stuff to touch, it’s about knowing what not to touch. -Buddha Linux
Linux is really about the changes you don’t make
Breaking Linux just shows you what not to do next time.
Me, cursing at my lack of sound:
“Maybe I shouldn’t mess with my audio server config…”Me, finally having fixed it:
“I’ll fucking do it again”
lmao for real. i’ve been so tempted to just get a system76 and be done with all that. randomly losing audio in the middle of doing anything is so obnoxious.
I haven’t had any issues with it since the last time fixing it. There’s a single app (Steam) that forgets its audio settings on reboot and every update replaces the launch script I use to help it remember, but even so, it runs perfectly well.
It’s just that every time I do decide to mess with it, I end up with a silent reminder that I have no idea what I’m doing. Then I tinker some more and it starts working again and stays stable so apparently it’s correct now and I’m not sure I understand why. So I decide to leave it be, until the urge to try something new becomes overwhelming…
“Never touch a running system” is for cowards. And reasonable people, I guess. I suppose I’m neither.
This is kinda why Bazzite is the only distro I can recomment to my gaming friends. The default settings work well, and its very hard to break it because its pretty locked down and it pushes users to use flatpaks via the app store, which generally work great. It also does its own updates in the background (with a backup just in case!) so nobody ever really has to worry about it, and I really appreciate it for that.
Installed Bazzite once. Lasted about two weeks, before this hard-to-break-distro broke on it’s own.
Never did anything to it, it just started acting up.
Switched to CachyOS and it just works.
That’s a good data point I’ll keep in mind. Unfortunately cachy does not do nearly as much for the user out of the box so I can’t really recommend it to those friends, but it’s a great distro.
The biggest issue I’ve seen is knowing how to properly permission flatpaks, sometimes it doesn’t include default values that actually work and flatseal helps but I’m a techy guy and even I was bewildered looking at all the options the first several times.
I like the ability, I dislike the obligations to customize things to get stuff to work.
Like having to debloat windows before it’s usable.
Or like having to login to a microslop account to use offline tools
If I built a distro I’d call it Buddha Linux so every time someone points out something good in general Linux discourse I could say “that’s exactly how Buddha Linux is” and every time someone points out something bad I’d say “that’s exactly how Buddha Linux is”. It’s infinite marketing. It’s the absence of marketing.
Maybe not exactly the same, but Bodhi Linux is an Ubuntu derivative that develops the Moksha desktop environment based on the Enlightenment window manager.
That’s exactly how Buddha Linux is.
My man walked right into the trap while watching you build it
There is no trap. Only a pause on your path.
Change “ability” to “necessity”
You have the ability to break anything. Your distro, maintainers, developers also like to break things from time to time.
Don’t blame yourself for others breaking things.
Responsbility’s double edged sword
