Since it's sort of on topic can someone tell me why "=>" is better than "." for assigning or access properties / methods? Brendan seems to want to head this direction and I'm not too excited about it.
Nice. Down votes without explanation. Love it.
Ask HN: What will the post-Javascript era will be like?
31–33 of 33 posts
Re: Ask HN: What will the post-Javascript era will be like?
#32First, I'm going to assume you're talking about just the Web, and for that matter, just the Web frontend, because that is the only domain in which one can even pretend that Javascript is the "end of history". Outside of that domain Javascript remains barely a blip, Node notwithstanding. The end of Javascript dominance looks like the following: Step 1: Ship asm.js to every browser. Step 1.5: Do a complete job of bindi…
When I talk about the "end of history", yes, the web is the correct focus to read it. Yet, companies are demanding the devs to be more than frontend or backend devs. Look at the DevOps movement. JS allows your developers to work on both sides of the network with a single knowledge. It may become more than a blip, though I doubt it could ever takeover the backend or smartcards for instance. So your point (correct me i…
Devops implies many things including continuous integration, continuous deployment, as well as system troubleshooting and maintenance.
For server side JS, I am curious how many who believe in Node can troubleshoot below the application layer.
Re: Ask HN: What will the post-Javascript era will be like?
#33I don't think we're in a position to say. JavaScript is good enough and ubiquitous enough that a replacement will have to be pretty compelling. The only thing I see on the horizon that's actually got a shot at unseating JavaScript... is JavaScript. (EcmaScript 6.) Whatever replaces JavaScript will have to do the following just to get its foot in the door: * Run on every browser in use * No compile/build step required…
It's worth noting that ES6 actually does not run without compilation on every browser (and will not for a while) since it introduces breaking new syntax instead of stuff that could be polyfilled. For all intends and purposes it's a new language (it's like C++ to C). So maybe any other superset of JS would have the same chances.
Maybe, but I doubt it. ES6 is almost certain to get implemented in browsers. Other languages won't have that crucial advantage.