I hope you haven&#x27;t made your decision yet because the comments in this thread are extremely misleading.<p>First of all, please remember that <i>nothing</i> is faster than a properly written vanilla js application. Every layer of abstraction you add will necessarily slow your app down. You gain convenience at the cost of performance.<p>So unless you&#x27;re dealing with major issues in terms of complexity and understandability, I would ask yourself why you need to have a shiny new framework in the first place?<p>But let&#x27;s assume you do. You&#x27;re in the same boat that a lot of companies and developers are in these days - what the hell framework do I choose when a new one seems to pop up every day? Spoiler: there&#x27;s no right answer. I assume you want your app to be future proof, which is a fools errand, but supposing you&#x27;re a fool like the rest of us then my humble advice to you would be to read up on web components and choose the framework that embraces them the best.<p>That would narrow your choices down to Angular 2, Polymer, Aurelia, and probably some other less mainstream frameworks I haven&#x27;t heard about. Angular 2 would be a fine choice but it&#x27;s going to be a pretty radical shift to the way people do things, but it will come with a reward of up to 10-15 times the performance of angular 1.+ and react. Oh, and it&#x27;s not ready yet.<p>Aurelia takes a lot of its queues from Angular 2 but it&#x27;s basically production ready today and far simpler in terms of its complexity and API. It&#x27;s all-in on web components and has a very enthusiastic and helpful community surrounding it.<p>Polymer is Google&#x27;s <i>big</i> bet on the future of web development. It&#x27;s at 1.1 and production ready, and will be extremely well funded for years to come. It&#x27;s basically sugar for creating web components. It&#x27;s similar to React in that they encourage you to build your application out of nested components. It&#x27;s different from React in that it embraces the web components spec and the DOM. React has explicitly stated multiple times that they have no interest in web components.<p>Polymer isn&#x27;t quite as simple to get up and running with as React and Google needs to address that, but it&#x27;s getting better. But the big thing the polymer team has going for them is that they literally share desks with the Chrome dev team, and as such they have their finger on the pulse of cutting edge web browser technology. The React core team doesn&#x27;t have that luxury, so they&#x27;ve taken the radical approach of trying to abstract away the DOM completely. It&#x27;s an intriguing approach but in my humble opinion it&#x27;s hostile to the open web. Make no mistake that Facebook is doing what&#x27;s best for Facebook. Google is doing what&#x27;s best for Google, too, but that happens to align with the goals of the open web.<p>Anyways, I hope you don&#x27;t just jump onto the React bandwagon before giving your research a little more time. HN is an echo-chamber and the word &quot;React&quot; is just the latest echo you see bouncing around.