Knowing process' memory range

[Cypher]

Yes, there are definitely cases where C++ outperforms C#. In fact, given all else equal, and given tests that don't emphasize the benefits of garbage collection, C++ should usually outperform C#. But not usually by much (it depends), and not always. Plus the ease-of-development/prototyping in C# (for me) far outweighs the gain of a few milliseconds that I'll never see because it's eaten up in an input processing loop somewhere.

But, to each his own. I know that to C++ purists like Cypher, even mentioning scripting/VM languages is nearly heresy...

Haha. Maybe just a little.

Seriously though, I've seen some great things come from C#, but it definitely has both pros and cons. It's nice to be able to just "not worry" about a lot of stuff, but on the other hand, very low level libraries are a **** to write. Call after call after call to the Marshalling lib. **** that, gimme reinterpret_cast any day.

Most of the problems people have with C++ imo stem from the fact they're not using C++, they're using C with classes (if that). It's just not necessary 99.99% of the time to do manual memory management, worry about handle cleanup, etc etc. RAII objects are there for a reason, and its not hard to write your own. People also continue to use the old C libraries when the C++ ones are so much easier and safer to work with once you're familiar with them. Between the STL, exceptions, templates, automatic resource managing objects, etc etc. most of the features of C++ that improve code safety/performance/maintainability/reliability/etcetc go unused by people that are in this field (reversing).

Yes, C++ has some major problems, but all languages do. I don't use C++ for performance reasons (for most projects managed languages are more than enough, heck, even scripting languages normally are). I use C++ because I love the ability to get my hands dirty quickly and easily if need be (which is often the case with the type of software I enjoy writing).