Paint.net 5.2 alpha now runs on Linux

Paint.NET 5.2 alpha can now run on Linux via Wine, thanks to a new in-app Direct2D reimplementation that was largely generated with an AI coding assistant. Commenters debate the appeal of Paint.NET versus existing Linux tools like GIMP, Krita, and Pinta, noting its lighter interface but also its closed-source license, telemetry, and Wine-based limitations. A major theme is the backlash against the use of AI-generated code—especially from artist communities—which raises broader questions about licensing, ethics, and the future role of LLMs in software development.

Enthusiasm for Paint.NET on Linux

  • Many commenters are excited; some call Paint.NET their most-missed Windows app.
  • Praised as light, fast, and intuitive for basic editing (crop/resize/annotate) without the complexity of GIMP/Krita.
  • Several say it “hits the sweet spot” between MS Paint and full-blown editors like Photoshop/Krita.

Technical Approach: Wine and Direct2D

  • This is not a native port; it runs via Wine.
  • Main blocker was Direct2D. Wine’s implementation is incomplete, especially for anti-aliasing and more complex graphics/text features.
  • The developer added an internal, from-scratch Direct2D reimplementation used only under Wine, in a dedicated DLL.
  • Some discuss whether swapping Direct2D/Win32 for cross‑platform stacks (e.g., Skia, Avalonia) might be easier long‑term.

AI-Generated Direct2D Layer and Backlash

  • The Direct2D reimplementation was largely generated with an LLM (“Claude Code”), with ~180k lines of “vibe coded” (lightly reviewed) code.
  • Developer describes it as “clean-room reverse engineered,” which multiple commenters question when an LLM is involved.
  • Bluesky backlash is noted as intense, largely from anti‑AI or artist communities who see AI as exploitative of scraped work and threatening livelihoods.
  • Others argue the reaction was disproportionate, especially for a free (though not open-source) app, and see AI codegen as a reasonable engineering tool.

Licensing, History, and Distribution

  • Paint.NET began as an open-source project, then went closed-source around 2008–2009.
  • Debate over MIT license: some say it “does not require credit,” others insist attribution is exactly what it requires.
  • The closure was motivated by people repackaging the app without credit (“backspaceware”); some criticize benefiting from earlier “open-source alternative” branding.
  • Current proprietary license and telemetry draw criticism; may limit inclusion in some Linux distros, though third‑party packages (AUR/Flatpak) are expected.

Alternatives and Forks

  • GIMP and Krita frequently mentioned as powerful but heavier/more complex.
  • Pinta is based on old Paint.NET code; users report a familiar UI but also long‑standing bugs and crashes.
  • Other tools noted: KolourPaint (very simple), Photopea (web‑based), PixiEditor (cross‑platform C# editor).

Quality, Stability, and “Runs on Linux” Debate

  • Current Wine-based support is labeled “extremely experimental”; some report it’s buggy and slow and warn against using it yet.
  • Debate over whether software via Wine “counts” as “runs on Linux.” Some see Wine as just another runtime; others emphasize poorer integration vs native apps.

LLMs and Future Clones

  • Thread includes speculation on using LLMs to fully clone Paint.NET or build similar editors, with rough token/time estimates and skepticism about post‑generation polishing and testing effort.