.NET on Linux – bye, Windows 10

Re:.NET on Linux – bye, Windows 10 by ygra on Monday October 17, 2016 @05:44AM (#12723702)

I remember that ages ago the Mono team used Paint.NET as a testbed for how complete and usable their System.Windows.Forms and System.Windows.Drawing implementation was. But back then Paint.NET was still open source. By now the source code isn't available anymore and it has grown a lot of things that are implemented in native code for performance (set operations on selection regions) or talking to things that have no equivalent in .NET (DirectWrite). It also uses WPF for a few things, so isn't completely Windows Forms anymore either. As it currently stands, Paint.NET is very much a Windows program, despite being written mostly in C#.

[ Parent | on HN ]

Re:.NET on Linux – bye, Windows 10 by egeozcan on Monday October 17, 2016 @06:55AM (#12723961)

Oh I didn't know that Paint.NET closed source. I found a blog post about the decision, an interesting read. Here it is:

https://blog.getpaint.net/2007/12/04/freeware-authors-beware...

[ Parent | on HN ]

Re:.NET on Linux – bye, Windows 10 by Tharre on Monday October 17, 2016 @08:43AM (#12724500)

I don't get it, one doesn't need the source code to change a few credits strings and pictures. Making Paint.NET closed source is about as effective as game studios putting more and more advanced DRM mechanisms into their games.

I understand why the author is upset, but his cure is worse than the disease.

[ Parent | on HN ]

Re:.NET on Linux – bye, Windows 10 by coldpie on Monday October 17, 2016 @10:14AM (#12725173)

Yeah, closed source tooling is garbage. I need to be able to fix the tools I use, or customize them for my purposes.

[ Parent | on HN ]

Re:.NET on Linux – bye, Windows 10 by flukus on Monday October 17, 2016 @08:36PM (#12731093)

I would of thought a proper OS license would've been a better solution.

[ Parent | on HN ]