[anonygler]

If only Google were as committed to its products as they are to the insanely over engineered proposals that fail to solve any legitimately useful use cases. Half of why these projects exist is for internal gate keepers at Google to make excuses for why they're not allowing productive engineers to adopt React/Vue, etc.

These weird quasi-frameworks exist in large part due to production use of NodeJS being banned at Google. What you get with Google OSS is a weird backwash, digesting external technical direction in a way that caters to internal consumers. They then flop it onto the ground on Hacker News.

Why would I use this? There's a million reasons not to, and then there's having a safe cushy jobs and priorities that have nothing to do with the core business.

Bleh.

[rictic]

This is, uh, a pretty confused set of things to say. Shadow DOM is implemented in every browser. Now that we've dropped IE11, Lit doesn't need any polyfills in any of our supported browsers.

Lit is javascript, and would greatly benefit from Google's internal stack having better support for NodeJS.

[anonygler]

Fair, removed that part -- I remember something about Shadow DOM got delayed or had a lot of push back, back in the day -- and I thought it was dead in the water when I started seeing Shady DOM stuff internally. But regardless, I've never had a single use for it working on SaaS products.