This is a well written piece.

I’ve built production systems in Angular 1, Ember and now React at Netflix. I’m also a lead contributor on RxJS 5. I collaborate frequently with the angular team. But I don’t really have any favorites here.

The bit about the size of RxJS is quite inaccurate (as I commented).

I also think any compile-time advantages you think you’re gaining with React are going to go away in very short order, if they’re not already gone. I’ve seen some pretty compelling work in angular 2 regarding compile-time optimizations and static analysis.

One thing this article doesn’t touch on is the principle of least power. The idea is that you use a language with the minimal amount of power to support your needs. A template language is ideal for producing DOM in this regard. JSX does give more power and flexibility at the cost of possibly giving too much power. Arguably angular might also be providing too much power with the expression engine it provides to its template language. It’s debatable, but worth mentioning, IMO.

Other interesting things I’ve heard about for angular 2 are a CLI tool, and some tree-shaking and specific minification niceness for TypeScript.