(Nov 1, 2012 04:13 AM)Han. Wrote: Then learn.
You don't get anywhere by looking at something, thinking it's too hard and then walking away 🤝
Again, some very valid points.
However, a Hello World in Assembly is almost certainly going to be faster.
My point was that once you get into programs that are industry sized and being used for a company, if the programmer hired is awful at Assembly but a guru at C, then the C code will be good and the Assembly code will be bad, which in some cases could lead the the C code actually executing faster than the Assembly.
Obviously the programs that would apply to would have to be big enough so that it actually had some differences to it because you can't do everything in C the same as in Assembly, you have to find different ways.
Ya, I agree with you that it depends on the programmer and his good habits to write less code as possible and be efficient.
Just saying that the ASM language itself can give you that speed edge if you follow good programming practices. The language itself will make the program faster however if you lets say use Windows 32 api to draw the windows and menus then that be the same speed as C. Since the code is the same. Their might be a small speed difference with ASM. It could execute your ASM commands faster then C commands. So not talking about the API but the code where you utilise the api. That could would be faster but not by much and it won't make a significant change in speed. Nothing that is noticeable.
I am just saying that ASM can make your programs faster but that's only if you use ASM to right the code more rawly or towards the o ring levels. AKA the more direct code.
ASM gets translated to op codes which is the most direct programming you can do towards hardware. So for like an OS if you can do system calls to the OS's kernel that will be quicker in speed to execute then using an API that does the same thing but has a lot of fuss on top of it.