Angular 2 versus React
There are some slight inaccuracies here, such as file size reporting - Angular 2 is fat at the moment only because it is bundling the whole kitchen instead of just the one piece that is the library itself. The Angular 1 number also is off too - this link is giving me 52.8 KB for example (minified + gzipped): <a href="https:&#x2F;&#x2F;ajax.googleapis.com&#x2F;ajax&#x2F;libs&#x2F;angularjs&#x2F;1.5.0-rc.0&#x2F;angular.min.js" rel="nofollow">https:&#x2F;&#x2F;ajax.googleapis.com&#x2F;ajax&#x2F;libs&#x2F;angularjs&#x2F;1.5.0-rc.0&#x2F;a...</a> (all numbers I remember seeing for angular 1 were around 120 KB IIRC). I&#x27;d suspect all the other numbers are off too, but I haven&#x27;t investigated.<p>There is a strong argument against doing what JSX does in moving the HTML to JS - you allow developers to fall into the trap of creating complex conditional DOM that is hard to read without a disciplined team (if statements all over the place with imperative DOM construction for example). Neither approach of JSX or Angular&#x27;s templating (or any other similar system to either) are without its warts, and this falls into an opinion discussion without real winners excepting for however a particular team prefers their templating.<p>One thing that wasn&#x27;t discussed but that may come into play - the performance numbers out there for Angular 2 currently is extremely impressive. Optimized Angular 2 code is generally performing at about 2x the rate of other frameworks&#x2F;libraries out there for UI rendering&#x2F;repainting, and unoptimized Angular 2 code is performing at roughly the same parity as optimized React code (although optimized&#x2F;unoptimized React code performs very similarly in many situations, which is a huge benefit of React).<p>I&#x27;m personally on the Angular side of the fence, I prefer the more declarative style to avoid the imperative DOM construction, but I could work with either (and have worked&#x2F;am working with both) if they are done right. Both are impressive libraries though, and both have strong merits - at the end of the day, it comes down to how your team works, and what they&#x27;re productive with. Both libraries are bringing excellent changes to how we do things in the frontend...I just wish tooling was there in maturity, that seems to be the greater pain point currently.