But why?
Probably because having two separate dependency management solutions can lead to a lot of needless headaches.
And it makes particular sense for Gnome to switch over, since Gnome is focused on user space apps. Flatpaks should generally be more relevant and lower risk, long term, since they don’t require root privileges to install.
without some sort of clear ‘Linux Certified’
I think we will get there. Ironically, we might have ‘Steam Certified’ first, for alternate SteamDeck hardware.
I’m the meantime there’s premium brands like System76 and Framework who are making Linux support part of their brand image.
Needing ndiswrapper was bad, but Ndiswrapper was salvation (okay it was fixed wifi, which is practically the same thing, to me…)
Yeah. I’m confident in this change thanks to my equal discomfort configuring either SELinux or whatever OpenSUSE has. Hooray!
But joking aside, this sounds like a good thing and I appreciate all the folks who do understand that stuff and have worked hard on it.
Plan to share a link so the hackers can check your work?
I’ve heard good things about vibe coding primary use cases for common problems.
I have experience vibe coding unusual use cases. The AI was worse than useless for those.
So I’m curious how the corner cases and security stuff on common problems turn out. (I always get that kind of thing from a library, so I have no experience vibe coding those cases.)
(Genuinely curious. And obviously, no worries if you don’t want to risk sharing.)