4 ms·
I'm not sure I agree with the sentiment that "React is in the past". According to the 2024 State of JS, [it's still used by 67% of engineers](https://2024.state
by pupatlas 1y ago
I'm not sure I agree with the sentiment that "React is in the past". According to the 2024 State of JS, [it's still used by 67% of engineers](https://2024.stateofjs.com/en-US/libraries/front-end-frameworks/#front_end_frameworks_work https://2024.stateofjs.com/en-US/libraries/front-end-framewo...), compared to just 4% of engineers using Lit. If I were to make a library out of this, I'd want to target the largest cohort of developers I could, so I'm not sure writing one in Lit makes a lot of sense.
As for your first comment though, me too! I love abusing CSS :P
- dtagames 1y agoFrameworks largely came about because native web components weren't built into the browser. Now, they are. So naturally the old method is more entrenched. You can write it as a native web component and ship something that works with React and without React.