[troupo]

> Not being tied to the JavaScript industry upgrade cycle (which is short!),

> We currently use Lit for the framework on top

These two are contradictory statements.

1. lit is both newer than React, and started as a fully backwards incompatible alternative to Polymer

2. Despite being acrively promoted as "not a framework just a lib" it's rapidly sucking in all the features from "fast moving js": from custom proprietary syntax incompatible with anything to contexts, a compiler, "rules of hooks" (aka custom per-dieective rules) etc.

> We're currently on material components and migrating some to Shoelace.

Again, this is exactly the "fast js churn" you're talking about.

[spankalee]

Lit is fully compatible with Polymer (and any other web components).

[troupo]

The output of lit is.

Not lit.

Stop pretending this isn't the case

[spankalee]

I can't even tell what you're arguing.

Lit helps you write web components.

Those web components are interoperable with other web components made with Polymer, Stencil, FAST, etc...