• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • I mean the Gimp in particular. My point is that if we could suddenly wish the Gimp into non-existence (a counterfactual) then we could get a do-over. But because the Gimp actually exists it occupies a niche that could go to something better. Instead of banding together to create a better tool, people just grumble a bit and then use the Gimp (or hand over their wallet to Adobe).


  • I think my biggest issue with the Gimp is that it simply exists. If it didn’t exist there’d be a huge hole in the free software space and people would get together to build software to fill it. But of course there’s no guarantee that would actually produce something better.

    Maybe the real problem with the Gimp is that it’s built to scratch an itch for its own developers who are used to its bizarre UIs and workflows. For all the people I’ve seen complaining about the Gimp over the years, none have stepped up to create an alternative. I think this is likely due to the intersection between visual arts people and software engineers being extremely small (and likely most working for Adobe already).






  • The issue is that you don’t want to give some random untrusted process root access. You, the user, have root access as long as you’re capable of running processes as root, but that doesn’t mean you should.

    There could be tons of apps on the iOS App Store or Google Play Store that are completely benign under the existing security model but do nefarious things when run as root. No one knows that for sure because they aren’t tested under root by Apple or Google.

    The problem with root is that it’s giving the process the keys to the Ferrari. That’s long since been decided to be a bad security model. Far better to have the process request permission to access particular resources and you grant them on a case by case basis.