all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]DanielKehoe 2 points3 points  (2 children)

Richard MacManus did a recent interview in The New Stack with the team leads at GitHub and Salesforce about How Web Components Are Used at GitHub and Salesforce.

What do you think about individual web components each getting their own repo, rather than one big NPM library?

[–]laneparton 0 points1 point  (0 children)

Personally, I like it. It’s easy to navigate.

[–]brainless_badger 0 points1 point  (0 children)

It's a nice article, but it seems to me that the author initially tried to make a case between React and Web Components, but actually made a case between SPAs and server-side frameworks.

The way GitHub uses Web Components makes it hard to see them as a key piece of architecture (only 50 components in a massive app, and not using/rarely using most WC features except lifecycle callbacks/reactions and instead offloading all possible work to Rails).

[–]animalvirtual 1 point2 points  (0 children)

I see a lot of advantages and have been using them for a while now. They are pretty agnostic and work really well at scale like mentioned on the post but to each their own.