haunted

You can get the same thing with lit-html and any of the add on libraries that flesh it out. For example, Haunted is a react hooks implementation for lit: https://github.com/matthewp/haunted Choo suffered from not having an ecosystem, same with mithtil and other "like react but not" also-rans.

One thing that is particularly important to take into account when comparing web components to framework is that they can and should work together. If indeed "web components" replace your "framework" it will most likely be because a new framework that takes advantage of web components and all that the web is now replaces your old framework. Already libraries that combine popular concepts like hooks from React with web components (https://github.com/matthewp/haunted) are pointing the way to a more powerful future for both site that need just that little extra something via a stand alone web component or a whole family of components wedded to a framework into a rich application. That being said, don't get confused by people on either side being overly defensive of their place in the web ecosystem things are they are now will change. Techniq

lit-html is great! - no build step - ergonomic - fast - flexible - useful whether alone or in a library/framework wrapper (see LitElement, https://lit-element.polymer-project.org/, Haunted, https://github.com/matthewp/haunted, et al.) Getting just about all the convenience of JSX with the ability to have your templates run in pure JS in the browser, with no build step is pretty rad. Even if the difference is just a few seconds here or there, multiply that by the amount of work I'm supposed to be getting done in a day, and it starts to add up. It's also nice to have control over whether to work with attributes or properties. A level of control that is mirrored by having direct access to event binding (rather than an abstraction of it) so you can pin down whatever custom events you might be passing around your application. Maybe that's my f