k, so do programming in ASM. Its "overral performance" runs out all of your stuff...
If you feel like defining some action context:
- graphical programming? skip java, swing performs bad.
- heavy networking both on client/server? skip c#, m$-servers are bullshit
- 3d graphical programming? rate the framework. you probably wont do this from scratch asking this kind of question on epvp.
There is such thing as "the best performing programming language", this has been discussed countless times on these forums.
Pretty sure if I was to write a program in C++ and you were writing one in Asm then mine would have better performance (Not talking about smaller programs tho.)
Why? Because the C++ compiler will probably optimize the asm better than the asm you're writing.
Pretty sure if I was to write a program in C++ and you were writing one in Asm then mine would have better performance (Not talking about smaller programs tho.)
Why? Because the C++ compiler will probably optimize the asm better than the asm you're writing.
Your assuming that the person writing the ASM isn't experienced, and your assuming that you are experienced with C++.
It would take far longer, but if someone has 30 years experience with ASM, chances are they can create better performing apps than someone who writes in C++.
It would take far longer, but if someone has 30 years experience with ASM, chances are they can create better performing apps than someone who writes in C++.
30 years of experience with ASM is hell of a lot for there to be 'chances' though their argument is invalid, the whole proposal of using ASM is ridiculous.
30 years of experience with ASM is hell of a lot for there to be 'chances' though their argument is invalid, the whole proposal of using ASM is ridiculous.
He's probably referring to understanding how C++ applications are built. Like, a programmer with knowledge on computer microarchitecture or assembly has a much better chance of creating a better, more efficient application than a generic Joe programmer does. Understanding how C++ compiles code and how assembly is interpreted really gives the knowledgeable programmer the edge.
He's probably referring to understanding how C++ applications are built. Like, a programmer with knowledge on computer microarchitecture or assembly has a much better chance of creating a better, more efficient application than a generic Joe programmer does. Understanding how C++ compiles code and how assembly is interpreted really gives the knowledgeable programmer the edge.
I think what I was actually saying was that someone who knows their craft is going to produce better work than someone who is less experienced using more advanced tools.
This entire thing is extremely subjective, you can pick and chose scenarios which fit your argument.
