Echo JS 0.11.0

This is Regex, not NLP.

This framework is already outdated. Not built with ES6 in mind at all.

The performance metrics are also a sham. So your competitor is 360% slower? What do you even mean?

The Angular team must be pissed. On paper at least, this framework does (almost) everything Angular 2.0 is supposed to be, with a simpler API—and almost a year earlier. 

Not sure what the success of Aurelia will be in the crowded framework market, but it sure is something to watch.

The main problem with AngularJS is its module system and forced DI. And that can least theoretically be fixed.

If DOM performance is a concern, there would be nothing stopping AngularJS from e.g. using HTML templates to generate a VirtualDOM just like React.

It does depend on the use case. If you have a website that requires authentication, you can load the whole code while the user logs in. In that case, SEO is not an issue either already now.

It also does depend on your market. Certainly there are some markets where you might have to eek out every last bit of reduced latency. But if your market is a country where nobody has a connection of less than 10MB/s on their desktop OR phone then you can have a 1MB codebase plus stylesheets compressed to ~500KB and served by SPDY/HTTP2 downloaded, decompressed and running in less than 250ms. Why would you then ever go through the additional work of rendering on the server?

I was referring to Google planning to execute the JavaScript on websites it crawls in the near future. If that becomes standard, as it soon might have to, it would solve the SEO issue. The search engines are under pressure to sort it out on their side lest they become blind to a big part of the web — and yes, they will sort it out.

The first rendering would be almost always — though not necessarily — slower on first load. (An empty page + a simple JSON call + DOM injection has the potential of using less bandwidth than static HTML, but of course JavaScript applications are becoming quite large these days). After the first rendering though, it would generally be much faster. JSON uses much less bandwidth than HTML and you can do much more sophisticated rendering on the client than you could do on a server at no extra cost.

Angular 2.0 seems to be giving a lot of people the creeps now that details about it have been revealed at ngEurope. I'm personally quite positive about it. Directives have to be simplified or Angular will be replaced by something else.

A different novelty that was presented at ngEurope was the upcoming new Angular Router that will be released for both 1.x and 2.0. It will allow nesting Angular apps and support better decoupling. 

By the time 2.0 comes along it is imaginable that you will not have to upgrade your whole application at once — since it may already be decoupled into several smaller applications that can be upgraded separately. This could help a great deal in future 1-to-2 migrations.

What now is wrong about client-side rendering?

Hash routing? It's obsolete anyway. Speed? Client-side rendering can be (and often is) faster than server-side rendering. The only reason we still do server-side rendering, on the other hand, is because of SEO — and that roadblock is about to disappear as well.