Re:Web Components Will Outlive Your JavaScript Framework
by claytongulick on Wednesday October 25, 2023 @11:02PM
(#38021185)
> What churn are you referring to?
I think most developers are very familiar with the framework churn that I'm referring to.
In my case, I've been dealing with it since the 90s.
So my biases are there for a reason.
Re:Web Components Will Outlive Your JavaScript Framework
by troupo on Thursday October 26, 2023 @01:33AM
(#38021975)
"vast majority of users", "should be able to extend".
What are the cases when this easy no code upgrade fails?
And yes, v2 update is quite a breaking change
> Polymer was a WebComponentsv0 library
It wasn't. It got upgraded to v1 almost immediately
I’m quoting directly from here: https://lit.dev/docs/v3/releases/upgrade/
“For the *vast majority* of users there should be no required code changes to upgrade from Lit 2 to Lit 3. Most apps and libraries should be able to extend their npm version ranges to include both 2.x and 3.x, like "^2.7.0 || ^3.0.0".“
And here is v1 to v2 for completeness sake: https://lit.dev/docs/v2/releases/upgrade/
Most of your examples are kind of odd. One of them was a brand change that involves no code at all.
There is only one meaningful bit of churn in there which also was an overlay of the Web Platform itself.
Polymer was a WebComponentsv0 library
Lit is a WebComponentsv1 library.