>The source got deleted, what is the backlash even about?
It's Bluesky, they hate AI so the mob bullied him to delete the posts
https://web.archive.org/web/20260901203707/https://bsky.app/...
>Paint .NET-on-WINE has never been possible because of Direct2D, which WINE has really struggled with (for good reasons).
>So like ... why not reimplement Direct2D-in-Paint .NET? Remove the dependency on WINE completely. Clean room reverse engineering ...
>Thanks to Claude Code, it's now a reality. More story in the link above.
>It's buggy and slow, but real progress is being made.
>And I have no idea when/if this will be "production ready" or "supported" or even "good enough." Maybe next year, maybe next month, maybe 2035.
>Claude made more progress on this in 3 weeks than we've seen in the 12 years since PDN started using Direct2D in 2014.
>This isn't to talk down to the WINE folks, btw. Direct2D has a really complicated effects system, and probably only PDN really uses it, so the ROI was very low.
>AI doesn't care. And it doesn't get tired. And this is the perfect task for it: it already has the design (D2D's docs and API), and it already has a known-good implementation of it and an app to test against and bang its head against.
>So that's what it did: it banged its head against d2d1.dll and paintdotnet.exe for about 3 weeks until it was able to boot up PDN. In WINE. For real.
>Here's PDN on .NET 10 win-x64, in WINE 11.14-dev, on Ubuntu, in WSL2, on Windows 11. And yes it works on real Linux too.