Linked by Thom Holwerda on Mon 8th Feb 2010 13:23 UTC, submitted by kragil
Thread beginning with comment 408340
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Well, you could copy&paste system-independent painting algorithms even if they were written in C++, so it is not much of an achievement. .NET and Java promised to take care of system-dependent stuff (like gui, networking, threads) too. The difference is that Java with SWT and Swing actually delivers on this promise.
and .NET w/ Gtk# fulfills that promise too.
Paint.NET isn't even hindered from running on Linux because it uses Windows.Forms, it's hindered because Paint.NET calls out to win32 C/C++ libraries.
If the author had chosen to use Java and SWT, it would still have the same problems.




Member since:
2005-11-09
Uh...
The core of the application that does all teh hard stuff was a copy and paste job. He rewrote it in Cairo so it could take advantage of the Linux GUI features that lack support if you are using Mono's winforms implimentation (which is just there for a convenience to get your .net app up and running quickly).
A Java app would be equaly as "portable" if the developer used a native set of widgits on windows that had limited support on Linux and OS X.