11–20 of 48 posts
Earlier quoted context omitted.
I'm well aware of js.next/harmony/whateveryouwannacallit. Come back to me in 10 years when it's implemented everywhere and everyone that was on an old version of browser X has upgraded to one with those features.
Or use a tool that compiles js.next to lowest-common-denominator-javascript.
Earlier quoted context omitted.
If we started over, we should pick a VM, not a language.
Some kind of flexible bytecode implemented across browsers would be fantastic, and you could always implement a fallback interpreter in javascript (or if feeling fancy, a decompiler).
i never thought that one day i will be the quy who posts this: try coffeescript, it really really helps (i would not believe it at first, either)
Earlier quoted context omitted.
Some kind of flexible bytecode implemented across browsers would be fantastic, and you could always implement a fallback interpreter in javascript (or if feeling fancy, a decompiler).
Isn't Javascript a flexible bytecode?
Earlier quoted context omitted.
Or use a tool that compiles js.next to lowest-common-denominator-javascript.
Yay a dynamic language with a compiler step.
There seems to be agreement that Javascript is a messy language which is popular by default: it was included in Netscape, then other browsers picked it up. Now we're stuck with it. I realize this would be very difficult and introduce horrible compatibility issues for a while, but sometimes I think, "what if we could start over?" What if Chrome and Firefox started supporting Python or Ruby or a custom, well-designed l…
1. User opens a page with scripts in LanguageX. The page links to some kind of VM configuration file. 2. Browser loads that file, which enables it to parse LanguageX. Browser caches that file. 3. From now on, the browser can execute scripts in LanguageX.
Although, this particular idea might be the case when too much flexibility would lead to issues in the long run.
i never thought that one day i will be the quy who posts this: try coffeescript, it really really helps (i would not believe it at first, either)
I'm not a fan of CoffeScript, it fixes the wrong problems. It's not the syntax that's the REAL issue, it's the fragmentation, lack of module system, etc.
i never thought that one day i will be the quy who posts this: try coffeescript, it really really helps (i would not believe it at first, either)
I'm not a fan of CoffeScript, it fixes the wrong problems. It's not the syntax that's the REAL issue, it's the fragmentation, lack of module system, etc.
Everything is an Expression (at least, as much as possible)
There seems to be agreement that Javascript is a messy language which is popular by default: it was included in Netscape, then other browsers picked it up. Now we're stuck with it. I realize this would be very difficult and introduce horrible compatibility issues for a while, but sometimes I think, "what if we could start over?" What if Chrome and Firefox started supporting Python or Ruby or a custom, well-designed l…
If we started over, we should pick a VM, not a language.
There seems to be agreement that Javascript is a messy language which is popular by default: it was included in Netscape, then other browsers picked it up. Now we're stuck with it. I realize this would be very difficult and introduce horrible compatibility issues for a while, but sometimes I think, "what if we could start over?" What if Chrome and Firefox started supporting Python or Ruby or a custom, well-designed l…