What is your view on maturity of web components and the frameworks used to develop web components? like polymer etc. Do you think it is production ready. Develop once and use it across any platform/tech stack is it really true? can a web component work without any bridging library with any front-end framework say Angular, React, Vue etc and also with other tech stacks like asp.net , java (where the UI frameworks used are different like JSP, razor html engine and also some does server side rendering). What is the future for web components?
I Believe that eventually web components will storm the community. If you think Polymer is too "heavy" (and it does have also performance issues) I invite you to test slim.js (slimjs.com). Disclosure: I'm the author. And I welcome any web-components enthusiastic to PR and Join and I'm willing to share time and code with other libraries.
In terms of maturity - it is production ready. All evergreen browsers support it one way or the other, currently some requires a small polyfill (but it's temporary until all will complete implementation of the spec). It's working, It's easy to develop, reuse and I really believe that this territory will be the next thing in front-end development.
I'm not a fan of Polymer anymore (it is too convoluted and is not performant) but I do like the core concept of web components. Lately I've been using Riot.js instead of Polymer.
Make sure whatever webcomponent solution you use is SEO compatible if that is important to your project.
I use Polymer 2.0 and it looks like Polymer 3.0 is going to make some React developers happier. But to be honest I prefer the earlier days of Polymer -- it was easier for designers to collaborate with you on projects, we had support for themes, and a GUI builder application.
The main problem that I see is stability. If you've been working with Polymer in the past you've probably rebuilt your apps 3 times to keep up with the changes in the spec. Chasing a spec, seems to be a waste of time. If you compare the adoption of React vs Polymer you see what stability can do to increase adoption.
Going back further to my Swing and JavaFX days, I think there are some really important lessons that one could take from the JavaFX community and shortcut a lot of the API thrashing issues that we've had to deal with. The whole "separate code from UI specification" issue feels like a throwback to the early 2000s. And the need for a GUI builder to make it easy to design an application is something else that was recognized early on in the evolution of JavaFX. Perhaps they could modify the Material Theming plugin to serialize it out as Polymer components.
With Polymer 3.0 a number of the tooling issues should be sorted out. But I'm not exactly sure if you're going to be able to use the Chrome DevTools to click into a series of nested components and find the one that isn't styled right.