The End of Native Code?

psycln asks: "An average PC nowadays holds enough power to run complex software programmed in an interpreted language which is handled by runtime virtual machines, or just-in-time compiled. Particular to Windows programmers, the announcement of MS-Windows Vista's system requirements means that future Windows boxes will laugh at the memory/processor requirements of current interpreted/JIT compiled languages (e.g. .NET, Java , Python, and others). Regardless of the negligible performance hit compared to native code, major software houses, as well as a lot of open-source developers, prefer native code for major projects even though interpreted languages are easier to port cross-platform, often have a shorter development time, and are just as powerful as languages that generate native code. What does the Slashdot community think of the current state of interpreted/JIT compiled languages? Is it time to jump in the boat of interpreted/JIT compiled languages? Do programmers feel that they are losing - an arguably needed low-level - control when they do interpreted languages? What would we be losing besides more gray hair?"

Comments

My head's going to explode!!!!!!

[ConceptJunkie]

It's "LOSING"! L-O-S-I-N-G! One "O". Just one.

The opposite of "win" or "gain" is "lose".

"Loose" rhymes with "Goose". It can be used as a verb, but it means something different than "lose".

Geez, doesn't anybody read any frickin' books any more?! If you read books once in a while, you would actually learn to spell.

OK, you can mod me down, I'm done.