4 ms·
I'm only guessing that it'll be another year or so before Angular 2 is in a release-ready state... It's a huge break from the prior version, and imho a good one
by tracker1 12y ago
I'm only guessing that it'll be another year or so before Angular 2 is in a release-ready state... It's a huge break from the prior version, and imho a good one.
The tooling will be the most interesting to me, I can only guess that they'll use node and traceur for building the output in a project to something a browser can use. I've been moving towards React (and Flux) as it lines up well with the way I've been developing with node. This just takes it a step farther.
As for the features that aren't well known, this will change and have to be learned. There's enough in the ES6 stuff that I'm running new development against Node 0.11 so that I can get generator support and some other language features in place. Though still using the CommonJS/Node style require() statements.
I do hope, that like React and its' tooling that the Angular guys have a compelling case and support for shared server/client logic and rendering as well as support for Browserify and Webpack+hot-reload. Though I like Webpack I think it goes too far from the node system, it is really nice however and I can see why others use it.
It's all really interesting... I'm curious to see where Polymer goes from here as well...