What does HackerNews think of panel?
Web Components + Virtual DOM: web standards for powerful UIs
Language:
JavaScript
We have been using a small bit of glue code to write Web Components declaratively with Snabbdom for a couple of years at Mixpanel: https://github.com/mixpanel/panel. Happy to talk further about our experience!
Yeah, the way we use web components at Mixpanel involves sticking to the vanilla APIs for lifecycle management, but we still need libraries to handle inter-component communication, state and rendering (see my discussion at https://engineering.mixpanel.com/2018/06/12/making-web-compo... and https://github.com/mixpanel/panel). I do hope some of these concerns eventually get addressed in the standards though.
Easy: web components have not implemented a single part of the original promise [1].
It's not Web Components that are happening, it's the dozens of frameworks required to make them work that are happening.
Even mixpanel's library "does so by providing an easy-to-use state management and rendering layer built on Virtual DOM (the basis of the core rendering technology of React). Through use of the Snabbdom Virtual DOM library and first-class support for multiple templating formats" [2]
Web Components are a very low-level extremely limited crummy DOM-based API that no one in their right mind wants to use. They are not happening.
---
[1] https://fronteers.nl/congres/2011/sessions/web-components-an...
We've been using Web Components + Virtual DOM to build our web apps for the last year at Mixpanel: https://github.com/mixpanel/panel. The biggest issues have been dealing with polyfill issues (especially Shadow DOM leakage) and versioning elements (given the global namespace issue of "registerElement")