Oh hey, that me! We at Adobe are investing heavily in web editors built with web component technology. Not just Photoshop, but Illustrator, Lightroom, and a number of brand new or in development applications across the company, as well.
We’re also leveraging web components to support interoperability of our design system across teams who still choose to use frameworks or have been using them all this time. In this way we ship https://opensource.adobe.com/spectrum-web-components/ and teams like fonts.adobe.com that have a long standing Angular app, or edex.adobe.com with their long standing Vue app or various recent acquisitions with their own technical decisions, can all consume Spectrum design without shipping their own implementation or rewriting their app to another stack.
The ease of building at depth scale for large applications and at breadth scale for applications no matter their architectural decisions has been a huge win for Adobe and our goals to drive consistency and quality across the company. The speed and scope at which we’ve been able to do so just wouldn’t be possible without web components.
So great to see all of these implementations outlines in one place. It’s particularly helpful to see the benefits these web components could bring to the file size of the JS in your application. Hopefully the great scores that some of these libraries are achieving serve as a challenge to the others to push for even better number across the board in the future.
I've used web components in production in two different companies and in a number of personal projects, so I'd say so. The move to official TS support is brand new, so you might catch some turbulence in that area. Polymer generally is about to make the move from 2.x to 3.x, so there could be some issues there. However, you can work with 3.x code now, and the official release should be in the next month or two, so getting started now might be just the right time.
I've already upgraded some of my extensions to the tagged template literal syntax. It's so much nicer than what I was working with before, and is tiding me over for IE11 support in lit-html. Pretty big wins all around. Next, I'm gonna have to take a deeper look at those TS decorators!
We’re also leveraging web components to support interoperability of our design system across teams who still choose to use frameworks or have been using them all this time. In this way we ship https://opensource.adobe.com/spectrum-web-components/ and teams like fonts.adobe.com that have a long standing Angular app, or edex.adobe.com with their long standing Vue app or various recent acquisitions with their own technical decisions, can all consume Spectrum design without shipping their own implementation or rewriting their app to another stack.
The ease of building at depth scale for large applications and at breadth scale for applications no matter their architectural decisions has been a huge win for Adobe and our goals to drive consistency and quality across the company. The speed and scope at which we’ve been able to do so just wouldn’t be possible without web components.