> I think you mis/underestimate the extent to which you have a component model already. What you already have is the equivalent of React's "functional component

> I think you mis/underestimate the extent to which you have a component model already. What you already have is the equivalent of React's "functional components," where the component is nothing but its render method. When we (Polymer folks) think of a component model, we think of a lifecycle. Being notified when you boot up, when you're activated, when you're deactivated, and when the state you care about changes. React has that, Web Components have that, lit doesn't. Agreed that there's a lot of baggage on the term `framework`, it's probably a good idea to taboo the word and break it apart into the pieces that we care about. IMO that's: - how big is the cost of adding the dependency – mostly this is the size of the library - how big is the ecosystem of code that it can play nicely with - are there well documented best practices - is there a complicated black box of internals that do a bunch of magic, or is it composed of small modular pieces that can be understood in isolation