News for hackers. Stuff that matters.
Re:"Future of JavaScript" doc from our internal "JavaScript ... by TillE on Tuesday November 12, 2013 @02:14PM (#6720148)
Yeah, a flexible bytecode VM seems like the ideal solution for browser scripting, rather than the awful kludge of "compiling" things to Javascript. I'm not quite sure why there hasn't been more effort towards that.
Re:"Future of JavaScript" doc from our internal "JavaScript ... by modarts on Tuesday November 12, 2013 @04:47PM (#6721430)
Re:"Future of JavaScript" doc from our internal "JavaScript ... by pera on Tuesday November 12, 2013 @06:04PM (#6722036)
> The key argument in favor of a language VM is the development process.

> If you’re writing JavaScript, your “compile step” is just refreshing the browser.

This is not a really strong argument: the development process could be exactly the same if your development environment automate certain task, as syntax checking (like with jslint), recompile when the sources have changed (ie file watch functionality), reload when save (like with tincr)...

Re:"Future of JavaScript" doc from our internal "JavaScript ... by chromanoid on Tuesday November 12, 2013 @06:17PM (#6722121)
people will want to choose their own language forever. not building some low level spec like asm.js or a similar bytecode like language is just a marketing strategy.