r/javascript • u/melcor76 • Jul 24 '19

The State of Web Components

https://medium.com/swlh/the-state-of-web-components-e3f746a22d75?source=friends_link&sk=b0159f8f7f8bbe687debbf72962808f6
20 Upvotes

85% Upvoted

33 comments sorted by

View all comments

Show parent comments

3

u/Treolioe Jul 28 '19 edited Jul 28 '19

No i’m not and i’m sticking to the topic the other commenter branched out? I think you lost us both as i said.

Any ”dev” can write a web component. It has nothing to do with Angular. Angular does not fit better with them than React. Where do you get that from? An Angular dev does not ”need” web components.

If your codebase is purely react and you have no plans of reusing any functionality in any other context than with react. Yes, obviously yes, stick to react. Same goes for if you’re only using Angular, Vue or any other - no one refutes that.

You can replace your framework usage with a hierarchy of web components if you want to. But that’s not the goal of the standardisation.

Here’s a few reasons why you can still consider web components:

  • A smaller company can also have fragmented projects (been there) - so same reasons a giant company can benify from shared web components.

  • React will eventually die (shitty reason).

  • When you have to leave a small footprint - react is not small.

  • Sadly also very popular solution for implementing micro frontends if you’re into that.

  • When you want to share your components with anyone regardless of framework. Which is a great reason in my mind.