FWIW, stupid design can do way more harm to an app's performance than the underlying run-time environment. I've seen apps in "native" C and C++, in .NET, and in Java that are all equally slow and memory-hungry (rule #1 -- plain old data should not be modeled as objects... but that's a rant for another time). The poorly-designed stuff is not the work of amateurs either -- and this is stuff that is sold for ridiculous sums of money. Sometimes working in this industry makes me kinda nauseous.srg wrote:BTW I'd rather program in asm than .net personally, IMHO moving away from native code programs for general use is a bad idea and will lead to slower computers guzzling more and more processing power and memory. Fine for prototyping and small programs, but not large applications.
That said, I don't see much point in using asm for application programming anymore. If anyone doubts this, try working over 100,000 lines of enterprise software with a profiler and you can tell me whether hand-writing bits of it in assembler will do any good whatsoever.
In my experience, it's misused algorithms, naive mis-application of OO design, thrashing of the heap (too many new's and delete's in C++), inappropriate use of threads (having them wait for each other unnecessarily, or doing background tasks on a UI thread), and long network delays that make the performance of many apps suffer. Save the asm for what it's for -- OS/driver/firmware dev., and optimization of really performance-critical CPU-intensive code (game engines, whatever).
End of rant, back on topic...
