Hacker News new | past | comments | ask | show | jobs | submit login

The major improvement for everyone is decreased startup time thanks to Multicore JIT. That was one of my few irritations with Paint.NET.

Paint.NET should perform better overal thanks to GPU acceleration and multithreaded rendering. I've personally used the alpha's and beta's for a while now and it just feels zippier.




For several years I had put off using Paint.NET over GIMP due to the dependency on .NET, but as soon as I realized that it still managed to outperform GIMP, I moved on the spot.

Still do not get how GIMP gets compiled on Windows to perform so poorly.


JIT'ed bytecode only carries a ~10% performance overhead versus well-optimized compiled native code, so the argument that a .NET program would be slower is bogus nonetheless.

In this case, GIMP is fully POSIX and GTK based so it needs to translate all POSIX stuff for Windows + rely on a subpar implementation of GTK for the Windows platform.

A good example of how native vs managed usually impacts performance much less than the application structure.


Sure, I am aware of JIT vs AOT compilation, although .NET JIT has not been touched that much on the last years. Looking forward to RyuJIT improvements.

Just that a statement that writing something in C does not make it fast by itself.


Why wouldn't something like Paint.NET just be AOT compiled with ngen?


it's JIT compiling of the third-party plugins, which are dropped by the user in a folder and not AOT compiled.

  > Startup performance when many plugins are installed is improved, thanks to the Multicore JIT feature 
Paint.NET assemblies are NGEN-compiled.


At least the 3.x versions were.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: