I think usually people need it for a specific use-case. I maintain a GUI app for Linux, Windows and macOS. All I need to do is generate and test a binary sometimes.
I think usually people need it for a specific use-case. I maintain a GUI app for Linux, Windows and macOS. All I need to do is generate and test a binary sometimes.
Just be careful about trying to run your AppImages on a distro with for example only FUSEv3, because there are system dependencies.
I tried out Arch for a while. The AUR is a bit of a wild west and at least I found it important to vet packages before installing them. It was a hassle. The same reason I only use one package from the OBS on Tumbleweed now.
I don’t believe iOS and Android use immutable filesystems to the extent some Linux distros do, like openSuse Aeon, Fedora Silverblue, Nixos, etc. iOS and Android just make it more difficult to gain root access.
I haven’t booted Windows since February and at this point I’m afraid to.
That’s not exactly my impression from following the design conversations through the years. They’re more approaching decisions from the angle of what they think is best, their philosophy is to plainly ignore what others do and follow their own direction. Of course taking inspiration from Photoshop might sometimes be a good thing, if it doesn’t conflict with the GIMP way of doing things.
I’ve noticed in recent years some newcomer devs have had discussions on how to design their contributions, mentioning Photoshop and other alternative ways and there were just conversations about the merits of the different approaches that could be taken and what would fit the GIMP best, without bias.
Anyway, I wasn’t aware that GIMP UX suffers, I’ve never used anything else and am happy with it. It seem logical to me, obviously with fewer features than Photoshop but how much can a couple of guys do and they’ve had to refactor most of the GIMP for 3.0, but that’ll open up for a lot of functionality being added moving forward…
But it was the X protocol that needed to be replaced.