Just to clarify, the "real" I used was a qualifier for the bare metal code description.
I'm not suggesting JS/Ruby/whatever code isn't "real" code, but it is pretty common to see people talk about some JS/Ruby/etc code being "bare metal", totally abusing the classic meaning of the term.
Examples (just a couple out of many dozens I've seen over the past few years):
Efficient JavaScript is great! But it isn't bare metal programming.
Also people will be writing low-level C/asm code on small devices for quite a long time yet. While it is great that you can get small "IoT"-style devices with the power to run a JavaScript interpreter, such SoCs are still really expensive by "chip whose cost must be factored into every device manufactured" standards.
I'm not suggesting JS/Ruby/whatever code isn't "real" code, but it is pretty common to see people talk about some JS/Ruby/etc code being "bare metal", totally abusing the classic meaning of the term.
Examples (just a couple out of many dozens I've seen over the past few years):
http://video.kiberpipa.org/jsmeet_slavic_performance_optimiz...
http://www.hyperscala.org/
Efficient JavaScript is great! But it isn't bare metal programming.
Also people will be writing low-level C/asm code on small devices for quite a long time yet. While it is great that you can get small "IoT"-style devices with the power to run a JavaScript interpreter, such SoCs are still really expensive by "chip whose cost must be factored into every device manufactured" standards.