I was really upset that I don't know all this about the future of JavaScript, and then I googled and realised this is from the guy who invented it.
The State of JavaScript - Brendan Eich
21–30 of 266 posts
Re: The State of JavaScript - Brendan Eich
#22> NaCl? Not portable. To dis NaCl on this basis and not even mention PNaCl is dishonest. http://www.chromium.org/nativeclient/pnacl/building-and-test... > Defined by implementation. As it should be, until the implementation settles and it's clear what interfaces should be standardized. What a waste of time it would have been to standardize the pre-PNaCl work, for example. I wouldn't expect Rust (for example) to be st…
Rust is never going to be part of the Web. Content will never be able to execute Rust code. If Mozilla had been proposing to integrate Rust as a potential client-side scripting language (which wouldn't happen to begin with), the process would have been totally different.
Re: The State of JavaScript - Brendan Eich
#23Aside from my personal distaste for his backing up the semantic truck and dumping it into ES6, I think it's a bit annoying -- to the point of being disrespectful -- that Brendan doesn't mention V8 in his history of JavaScript. Without V8, there is no JavaScript on the server-side (sorry, Rhino and SpiderMonkey), there is no Chakra and there is no TraceMonkey/JagerMonkey/IonMonkey: given that JavaScript had survived f…
I wonder what he would have said about TypeScript, it seems that it was launch after this conference (though there is a large chance he was in the loop, no pun intended)
Re: The State of JavaScript - Brendan Eich
#24Trying to read this on my Galaxy Nexus was a non-starter...
The first slide was a pita but once you get pas that its OK. I swiped over the top half of the screen in portrait. Google chrome beta.
Re: The State of JavaScript - Brendan Eich
#25Anyone executed this yet? http://brendaneich.github.com/Strange-Loop-2012/assets/image...
I tried running it through a few different free online OCR services and haven't had any success yet.
Re: The State of JavaScript - Brendan Eich
#26Kind of annoying presentation style quirk: but some slides are on a vertical stack which you can access by hitting the down arrow instead of going right. You can tell in the bottom right which directions are available from the slide you're on.
I just used the mouse wheel and it always went the right order, even if vertical.
Same, but it still seems unintuitive and pointless. Why not just keep them going from left to right? I'm pretty sure the target audience for this only really cares about the content and anything else just gets in the way.
Re: The State of JavaScript - Brendan Eich
#27Aside from my personal distaste for his backing up the semantic truck and dumping it into ES6, I think it's a bit annoying -- to the point of being disrespectful -- that Brendan doesn't mention V8 in his history of JavaScript. Without V8, there is no JavaScript on the server-side (sorry, Rhino and SpiderMonkey), there is no Chakra and there is no TraceMonkey/JagerMonkey/IonMonkey: given that JavaScript had survived f…
> I think it's a bit annoying -- to the point of being disrespectful -- that Brendan doesn't mention V8 in his history of JavaScript
Bullcrap. Why would V8 deserve any more mention than Spidermonkey (which had none, by the way) in a talk about the semantics and language evolutions of javascript when it's Gecko/Spidermonkey which pioneered and implemented roughly 95% of these evolutions in the first place? Why would it deserve more than Trident, which — through xmlhttprequest — is the one responsible for the vast majority of the language's actual popularity? Because it's your pet runtime and you dont like others?
> So it would be nice to see some respect where it's clearly due...
You may want to take this advice for yourself, your comment is dismissive, insulting, contemptuous and contemptible.
Re: The State of JavaScript - Brendan Eich
#28> NaCl? Not portable. To dis NaCl on this basis and not even mention PNaCl is dishonest. http://www.chromium.org/nativeclient/pnacl/building-and-test... > Defined by implementation. As it should be, until the implementation settles and it's clear what interfaces should be standardized. What a waste of time it would have been to standardize the pre-PNaCl work, for example. I wouldn't expect Rust (for example) to be st…
Rust is never going to be part of the Web. Content will never be able to execute Rust code. If Mozilla had been proposing to integrate Rust as a potential client-side scripting language (which wouldn't happen to begin with), the process would have been totally different.
On a side note, has there been any experimentation with Rust on NaCl or with Emscripten? I'd love to write some web demos with it.
Re: The State of JavaScript - Brendan Eich
#29> NaCl? Not portable. To dis NaCl on this basis and not even mention PNaCl is dishonest. http://www.chromium.org/nativeclient/pnacl/building-and-test... > Defined by implementation. As it should be, until the implementation settles and it's clear what interfaces should be standardized. What a waste of time it would have been to standardize the pre-PNaCl work, for example. I wouldn't expect Rust (for example) to be st…
> It's highly unlikely that JavaScript spit out by a code generator (this would be the competition for NaCl) is going to be at all readable. With SourceMaps it's possible to make them readable[1]. Also, problem with NaCl is it forces developers to move away to a different toolchain. Most developers would feel more comfortable and productive in developing in the browser, rather than moving to a IDE. [1] - https://wiki…
I don't think NaCl is targeted at web devs that are comfortable developing in the browser. It's targeted at the other devs that aren't comfortable with JS and who write C++ (or other) code (like in games or other graphic-intensive stuff).
Re: The State of JavaScript - Brendan Eich
#30I think he missed mentioning the new lambda syntax. Hope it's still in ES6. Also, my pet peeve: there is no language that needs await/defer as much as JS. EDIT: Maybe it could be done with macros, which is on its way.
> there is no language that needs await/defer as much as JS.
http://wiki.ecmascript.org/doku.php?id=harmony:generators
is a more general abstraction, which allows expressing async/await-type constructs: http://taskjs.org/