It’s great to see that Pipewire has reached this milestone. Personally I’ve been using it since 0.3.35 for very basic audio needs and it’s been a very smooth transition. After installation I never had to tinker with it anymore. “It just works”^TM^
Then you’re on your own. What the duck 🦆 do you expect to happen if you can’t even invest the 10sec to skim over a message (in the few events that there even is one) to see if it affects you and any manual intervention is required.
A fully functional system, just like any other normal OS?
You hit update - boom - you get one, seamlessly, with no breakages and no other user interaction. And that’s how it works pretty much everywhere - except, you know, Arch.
If you’re fine with it - that’s fine, go ahead and tinker all you like. But don’t expect others to have the same priorities.
Man that’s news from 2016, like, it’s a bit rare occasion, y’know. You’re way more likely to get borked by Arch even after reading all the instructions, and it did happen numerous times.
Touching grass is what I do when you take steps to intervene in your system to make an update work.
I see you are an Arch maximalist, but that goes beyond reason. Even Arch proponents are normally not as aggressive on the topic, and admit Arch is too complicated in that regard.
The only problem here is that snapshots (and btrfs for that matter) are not the default behaviour. I would really appreciate Endeavour having this as the default setup. It is very likely what you’d want.
Yes, Garuda does, even with bootable snapshots, but it’s otherwise not as clean as Endeavour. As far as I can tell, mkinitcpio/GRUB2 or their setup thereof causes more problems than it solves. My system was bricked multiple times until I switched to a dracut/systemd-boot setup, which works flawlessly since quite a while.
As for the user experience, there are 0 distros you should perform a (major) upgrade on without taking a snapshot first. I had broken systems after apt upgrade. From my point of view rolling vs versioned release are basically occasional mild vs scheduled huge headaches.
I think Windows does some things well, that are just worse in KDE
Ctrl+Alt+Delete, Taskmanager is actually privileged and can force close running apps. On KDE the same apps exist but they are not privileged enough. EDIT: of course it is privileged, but it doesnt even open if the “Desktop” hangs. There seems to be no privilege isolation, nothing left as security space for these tasks.
The UI is more stable, the bars dont weirdly load, App Windows just open in full size and not fly around. When an app crashes I can still use the cursor (often)
The Rest is crap, like everything. Updates are horrible and intrusive without a single reason. Immutable updates are so much better, regular Linux Distros probably cant compare regarding security.
Pipewire makes me feel like I’m a bit stupid. I keep reading about it, I read the introduction and FAQ on their website, yet I still couldn’t tell you what that thing even does. All I know is it’s a slightly less buggy drop-in replacement for pulseaudio, and pulseaudio is something I use because Firefox forces me to. (I would still be on plain old ALSA if it weren’t for Firefox.)
Also, it definitely did not “just work” for me out of the box, I had to do quite some digging and some very non-obvious stuff to get it to a) start up and b) let me use my microphone. I still don’t even know what “starting up” really means for pipewire (is there a daemon or something?), the website likes to pretend that isn’t a thing, but without doing some stuff to start it up, audio just won’t work for pulseaudio and pipewire applications…
I run PopOS on my IdeaPad Flex, which is one of those flip all the way around type laptop tablet hybrids, and it handles tablet stuff pretty well with the touchscreen, on screen keyboard, and stylus input.
In F/OSS, it is not unusual for software to stay below 1.0 version for a long time yet still get a lot of use. Just look at how long OpenSSL, for example, was at 0.9.something, while already being of crucial importance to a lot of internet infrastructure.
The reasons for this are varied, but the most important is probably simply that free software developers don’t feel the pressure to call a product 1.0 when they don’t believe it is ready to be called that.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.