Quote:
Originally Posted by RickS
Why did you pick C#, Mike? I would have thought that image stacking would still be more efficient in a compiled language rather than an interpreted/JIT one. Maybe I need to finally toss my old fashioned ideas about not wasting CPU cycles and memory. It's hard to do when you cut your teeth on embedded systems with 8-bit CPUs and KB of memory rather than GB  |
A very good question. Speed: Straight up, processing images in C# is at least three times slower than in C++. But C# makes using multiple cores, and parallel processing generally, a breeze. Next, C# provides the keywords "fixed" and "unsafe", which let you write more or less pure C++ in-line, though it's a bit of a fight. Finally, for real speed on some heavy maths, I use C++ DLL's. Grand result: I can zoom and pan a 16 megapixel image at 70 frames a second. Ease of use: Writing event handlers for the user interface in 1970 Borland C++ was easy. In Visual Studio C++ it is pure torture. In C# it's a pleasant doddle.
I kicked and screamed for about four months, but now I'd never go back.