To view parent comment, click here.
To read all comments associated with this story, please click here.
In the purest form you are correct, native code => compiled code in speed; However, in practice it is going to be just the opposite. First there is the fact that few coders are skilled enough, and for that matter patient enough to create large optimized programs in assembly. But lets say someone did spend the time and created an awsome O.S. in the i386 instruction set. What about other platforms, or even updates to the intel platform? Less well-written compiled code could very possibly reach higher speeds just becuase it can more fully take advantage of a platform with just a recompile.
You are right, in a big part the issue is about programmer qualities and the quality of the OS basis. The goal of the project, of course, is to provide a high-quality package at the end.
But at this point I see no difference: the same applies to other platforms. Going simple: bad programmers will produce bad code. No meter what platform they build on. On the other hand: good OS dev management and hight quality distribution building will let the talented developers to do their best in writing apps.
The thing they can't help is the small number of assembly developers out there. But a project like this definitly will increase the attractivity of the platform.





Member since:
2006-04-07
As it's already mentioned, you're wrong: a compiled code will never be as speed efficient as a native one. Except for the cases which are about programmer mistakes, of course.
Maintainability? Why do you think it's any harder than elsewhere? Portability? This is a new platform. Robustness? They're maturing the new platform - it will be in time, if they can stand up for their plans.
And... here's a note, ope you won't take this personal. You've heard something somewhere and you just belived that one without understanding. Be more careful next time, and try to be less offensive - at least think before you do claims like "infintely stupid".