At the moment, as many know, the annual Google I / O conference is taking place, as part of which a new version of the library for working with interfaces of web applications Polymer 3.0 was introduced (video in English):
Main innovations:
Eliminate the use of HTML imports in favor of ES-modules
Failure to use bower in favor of npm
Removing polyfills to support new standards (required for FF, Edge and IE11) from the library itself
Why can this be interesting?
A key feature of Polymer is that this library is built on the basis of the modern group of standards Web-components . This means that its compositional capabilities (largely similar to React or Vue) are not realized with the help of a meta-platform and js-abstractions over the usual DOM, but at the level of the browser itself, which opens up a number of truly remarkable possibilities and creates a whole range of new approaches. For example, the border between the SPA and the classic web page is almost erased, the work with the development environment is greatly simplified and the versatility of your solutions is significantly increased: you can use your UI library and the implementation of your design system in conjunction with almost any popular framework or library the need for any serious adaptation ( https://custom-elements-everywhere.com/ ). And that's not all.
PS
It so happened that I personally have been working with the set of standards of Web Components and directly with Polymer for several years already, since version 0.5. I am very closely following the development of this sector of the Web platform and have tried a lot in the combat conditions of real projects. During all this time, I regularly meet various opinions about this technology, both among domestic developers and among our foreign colleagues. And these opinions, in the depressing majority of cases, are either very superficial or deeply erroneous. I urge the community to take an unbiased look at this stack, to revise and update their knowledge. Believe me, it's worth it.