by issues I mean breaking existing users' workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).
There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That's it, everybody is happy.
So yes, he is the one causing issues. Because the issue isn't in the features he removed, but by breaking the users'expectation that the package they installed yesterday, is the same one they're updating today.
why is proper healthcare possible anywhere except there? Capitalism is not a us specific thing, so it can't be relevant. We have tons of counterexamples to your argument
i have one, it's not very good tbh. You would need to modify the software yourself to make it actually practical. some way to lock the screen, some way to vibrate more than one 250ms blip when an alarm is triggered, stuff like that.
if you don't play certain multiplayer games that use invasive anti-cheat software, then you really should give it a go! It's gotten to the point where I first buy games and then worry about compatibility. The vast majorityic just work with minor tweaks at the most (setting some launch arguments usually)
If you try to start learning how they work, the first thing you realize is that hallucinations are fundamental to how the technology works. Of course they are unfixable. That's literally how they work.
They're broken clocks that happen to be right more than just twice a day, but still broken nonetheless.
so they're the stubborn ones who keep wanting to make gnome different for difference's sake? If so, good riddance. Maybe gnome can start working on becoming my de of choice again
but they have a lot more disadvantages for most scenarios (if you're not a faang scale company, you probably don't need them)