4 ms·

People definitely still care about Web Components. They have evolved quite a lot over the last couple years, and there are some very nice helper libraries that

People definitely still care about Web Components. They have evolved quite a lot over the last couple years, and there are some very nice helper libraries that have come out for them (skate.js, stencil.js) I agree that state management/binding is hard, in general, but I'm sure that these Web Components helper libraries will be more and more sophisticated as time goes by. Also, isn't it pretty much standard to use redux/mobx for state management with React? Why not use these kinds of tools with Web Components? In the past I've used slots and symbols to communicate between parents and children without exposing all the guts of my components. Aside from that, there's not really any good reason I can see that React itself couldn't/shouldn't support Web Components at some point soon.

symlinkk 9y ago
If Web Components are only usable with a library on top of them, what is the point of using them in the first place?
- colordrops 9y ago
  Different libraries would then be compatible and interchangeable. You could mix and match web components using different or no frameworks on a page.
  - symlinkk 9y ago
    The guy I replied to is saying that he needs to use third party libraries just for state management and data binding. Pretty much every non-trivial component is going to need these features, and if they're using a library to get them, we're back to the same situation we were in before Web Components.
    - lomnakkus 9y ago
      Nope. The whole point of Web Components is that all of the innards of components are completely encapsulated in a component, the 'client' of a component only cares about setting its attributes and responding to the events that it emits. (And perhaps supplying external styles.) I also think your claim of having to use 3rd party libraries for anything non-trivial is false, but let's ignore that for now.
- muthdra 9y ago
  What about processors? You need entire operating systems for them to become usable.

symlinkk 9y ago

If Web Components are only usable with a library on top of them, what is the point of using them in the first place?

colordrops 9y ago
Different libraries would then be compatible and interchangeable. You could mix and match web components using different or no frameworks on a page.
- symlinkk 9y ago
  The guy I replied to is saying that he needs to use third party libraries just for state management and data binding. Pretty much every non-trivial component is going to need these features, and if they're using a library to get them, we're back to the same situation we were in before Web Components.
  - lomnakkus 9y ago
    Nope. The whole point of Web Components is that all of the innards of components are completely encapsulated in a component, the 'client' of a component only cares about setting its attributes and responding to the events that it emits. (And perhaps supplying external styles.) I also think your claim of having to use 3rd party libraries for anything non-trivial is false, but let's ignore that for now.
muthdra 9y ago
What about processors? You need entire operating systems for them to become usable.