4 ms·
> Ah wait no, you mean the new ones that virtually no one uses, right? This is exactly the point. Virtually no-one is using them (well, except for Microsoft, a
by azangru 3y ago
> Ah wait no, you mean the new ones that virtually no one uses, right?
This is exactly the point. Virtually no-one is using them (well, except for Microsoft, and Google, and Adobe, and Github, and Reddit, and NordHealth, and a bunch of others), whereas they are far more future-proof than any of the much more popular frameworks.
It will all change with time, of course. Just like there is no reason now to depend on jQuery. If only I could restart our app again, I would never have chosen React for it. And it worries me when I think how we are going to migrate off of it.
- nfRfqX5n 3y agoMost of those use Lit right? I’d be afraid to choose a library created by Google
- azangru 3y ago> I’d be afraid to choose a library created by Google I wouldn't :-) Lit is just a tiny wrapper over native web components to add reactivity to their behaviour; but what is more important, Lit positions itself as a gradually disappearing library, intended to be replaced with native browser apis as they are introduced into the platform (e.g. DOM parts to help with templating, etc.). Compare this ethos to any other library out there.