C/C++

Originally Posted by Arainach

On C# - I'm no expert (I've just been learning it for a couple of weeks myself), but the entire point of C# is that it's strongly typed and prevents a lot of low-level activities that C and C++ allowed to that end. MS calls it a "security feature"; the rest of us call it "a pain in the ass".

Well, this is what bothers me about programmers who pretty much rely on the ease of a high level language. It really isn't a pain in the ass, rather C# forces you into using proper programming techniques you should have learned from the start.

C# was designed mostly with network and internet programming in mind where a lot of proper programming practices need to be observed to maintain security. The problem is most C programmers simply never learned what those practices were and never had to face them being they only have dealt with a single local machine. As a result they had to make the C# language very ridged in hopes in doing so would teach programmers proper programming via the language structure.

Most amazing jew boots

Originally Posted by Magic

Isn't the whole point of high-level languages that you let the compiler generate all the Assembly? What's the point of using low-level code in the middle of C/C++?

Because even some of the best compilers do things you don't want it to. They do make mistakes fairly often and the only way to resolve the issue is to edit the generated assembly by hand.

There's nowhere I can't reach.

Originally Posted by BlueMikey

There are many applications where any improvement is worth it. Consider a program which is run billions of time every day versus the time it takes to code a function once.

Exactly. When you have a program where 1% of your code accounts for 50% of your runtime (which is VERY common) then why the hell would you not recode that 1% in Assembly?

This thing is sticky, and I don't like it. I don't appreciate it.