Don’t? But maybe also don’t gratuitously trash someone’s work?

I’m not saying their work is bad. But every abstraction is leaky and it’s a lot easier to find someone who knows how to use the native SDKs for AWS/Azure/GCP than someone who knows an obscure framework that doesn’t cover everything.

Your original comment went a fair bit beyond that assessment.

No. Adults aren't made of sugar. Meaning was clear and professional using layman terms.

> And why would I base my entire application on a framework by a tiny developer?

If we work like this we'd have no frameworks. Everything started from 0.

Frontends are pretty much always awful... They work until they don't and then you're invested and screwed.

I've become a much bigger fan of well-designed libraries. Do one thing and do it well, and preview a simple API for doing it.

Seeing the clusterfuck of the modern front end ecosystem, you act like that’s a bad thing.

But the two most popular front end frameworks that came out over the past few years didn’t exactly come from small companies.

Great, now do Linux. Or cURL. Or Clojure. Or Perl. Or Python.

Great tools can, and often do come from solo developers without large corporate backing.

So the top contributors of modern Linux are large corporations. cURL is not a framework

And isn’t that the ultimate in survivorship bias? How many other languages and frameworks would you have left you screwed if you jumped into whole hog in before they had popular uptake?

Linux was started by one man, and the qualification as “framework” is immaterial to your point.

And was it actually used or became popular before it was adopted by and had contributions from major companies?

Actually, yes! And you are conveniently ignoring the other examples that don't fit your world view.