Re: Why are we limited to JS in browsers - would a bytecode ...
by silentbicycle on Thursday November 11, 2010 @02:01PM
(#1894802)
I'm mostly thinking about how many of the problems highlighted in "Javscript: The Good Parts" have been fixed in Lua, while Javascript can't be fixed. Not a matter of design and taste, but outright bugs.
[ Parent
| on HN ]
Re: Why are we limited to JS in browsers - would a bytecode ...
by cpr on Thursday November 11, 2010 @04:35PM
(#1895367)
OK, don't use the "bad parts."
But it's a lot more than that. It's the "taste" of the language itself, and Javascript tastes much more like the kind of language I like using.
Lua always struck me as being so simple it crosses the line into Factor/Forth territory.
Re: Why are we limited to JS in browsers - would a bytecode ...
by orangecat on Thursday November 11, 2010 @07:21PM
(#1895982)
OK, don't use the "bad parts."
That's what I try to do, which turns it into a crippled Ruby. And there's no getting around it silently doing the wrong thing if I ever forget a "var" or "===".
Re: Why are we limited to JS in browsers - would a bytecode ...
by jashkenas on Thursday November 11, 2010 @08:02PM
(#1896090)
For what it's worth, there are tools that can help you avoid the bad parts. JSLint won't let you forget a "var" or "===" ... and if you use CoffeeScript, it's not possible to forget "var" or "===", because there aren't any.