React, Flux, GraphQL, Hack, HHVM...? All of this and more!
At Google I/O in 2016 there were two browser focused technologies from the company. These are the Polymer project and Angular 2. It might be a bit hard to make sense of why the company is investing in these two overlapping and competing projects.
Angular 2 is a compelete web framework that allows developers to build client side applications that run both on the server with Node.js as well as in the browser. It's a major revision to the wildly successful Angular 1.x and while making major changes internally, it's still the same product.
Polymer on the other hand is a project that aims to let developers use the latest native Web Platform features today. It's essentially an interim solution to provide a layer that will enable technologies that only exist today as specifications. In essence Polymer does not create any new features.
There are some overlapping aspects in Polymer and Angular 2 projects such as the use of the component model and the polyfilling of scoped CSS using various techniques (including native Shadow DOM).
Imagine if you would still need to download one of many modules to support CSS in the browser. Don't you think it's better to have that base level in the browser by default?
You'll likely feel that way about a lot of features that you get in Angular 2 today.
So the reason why Google continues investing in both Angular and Polymer is that they can play both the long and the very long game. Angular 2 will surely be around for at least five years in it's current iteration, but web platform standards will live on far beyond that.
With Google strongly footed in the browser game, they can steer the web towards adopting native components with their Chrome project. Evergreen browsers that continuously update to provide new features have been the norm for years.
The browser is the ultimate framework that you're targeting.Tweet