You know the exact feeling. You finally made the jump to Linux. You ditched Windows, installed your distro of choice, and felt the righteous glow of open-source freedom. Then you tried to edit a photo. And you realized, with a sinking dread, that you’d be stuck using GIMP for the rest of your life.
This week, the Linux community lost its collective mind over the Paint.net 5.2 alpha. Why? Because it finally runs on Linux via Wine. Read the forums. The relief is palpable. “This is by far the number one program I’ve missed since I left Windows years ago,” one user wrote. “GIMP is so unfriendly, Krita is for drawing, Pinta is a very shallow clone… Paint.net is just better in every way.”
Ideology is a luxury. When you just need to resize a photo at 2 AM, usability wins every single time.
Let’s be brutally honest: GIMP is a usability nightmare. It’s built by engineers, for engineers, and it feels like it. For years, the open-source community has told us to suck it up and use it because it’s “free” and “open.” But the moment Paint.net—a closed-source, Windows-first, .NET application—runs through a translation layer on Linux, we abandon our principles and cheer. Why? Because we missed the muscle memory. We missed the tool that didn’t fight us at every single click.
Here is the bitter pill the open-source community needs to swallow. Paint.net used to be open source under the MIT license. But its creator, Rick Brewster, closed the source years ago because people kept stripping his credits and passing it off as their own. In the ideological purity test of open source, closing your code is the ultimate sin. Yet, that decision might be the exact reason Paint.net is still so good today.
Software loyalty isn’t built on a license. It’s built on the friction you remove from a user’s day.
Open source without a strong, dictatorial product owner often leads to fragmentation, not quality. Look at the forks of dead projects. Look at GIMP’s decades-long stagnation. By closing the source, Brewster protected the design coherence of his vision. He kept the UX pure. “Open” doesn’t mean “better,” and “proprietary” doesn’t mean “evil”—especially when it actually respects the user.
For anyone building software today, this is your wake-up call. Users vote with their workflow, not their ideology. We will run your closed-source app through a janky compatibility layer if it means we don’t have to look at GIMP’s interface. The moat you are building isn’t your license, your GitHub stars, or your community goodwill. It’s the experience.
The market doesn’t care about your manifesto. It cares about whether your software gets out of the way.
Build something that respects our time, and we’ll cross any platform boundary to use it.
FAQ
Q: Isn't it hypocritical for Linux users to celebrate a closed-source app?
A: Absolutely. But it proves that users care about getting their work done more than they care about software licensing. Ideology is a luxury; usability is a necessity.
Q: What should open-source developers take away from this?
A: Your license isn't a moat. If your UX is hostile, users will jump through hoops to use a closed-source alternative running through an emulator. Prioritize design over ideology.
Q: Did closing Paint.net's source actually make it better?
A: Yes. By closing the source after people stripped his credits, Rick Brewster retained dictatorial control over the UX. It prevented the fragmentation that plagues many open-source projects and kept the design coherent.