KruzeS on 04 September 2007
Andir said:
It's good at taking a poor programmer's code and making it work. Microsoft has been doing this for a long time with their Visual Studio applications and even now .NET. Hell, a certain monkey like high ranking official even touted making the developer's lives easier in a recent conference. While it may sound great, it's bad for many... many more reasons than good. Developers don't even think about the processors anymore. Why is this bad? Because bad code doesn't show up in these situations. Coders that don't understand what the processor is doing and will blindly put in logic that make the processors perform many more tasks than are needed to perform a certain task. Ask your local developer what the fastest way is to multiply a number by 16. You'll get two answers. One is fast, and the other is lazy (or uneducated.) |
Who the bloody hell do you think you are to say such things?
I pray I never have to lay my eyes on a single piece of code you've ever written.
Reality has a Nintendo bias.