AcquiescentWolf

React is popular in the modern days only because, well, it's popular. Developers use it because companies use it, and companies use it because developers use it. It's not popular because it's better than all the alternatives, it's just that it has reached critical mass, and it's now "too big to fail". It takes constant effort to avoid React's many footguns. Supporters often call this a “skill issue,” but even if that’s true, why wouldn’t you prefer a framework that does the same things with less code, faster, and with far less mental overhead?

Ah yes, such large words like const, function, or return, that only exist in TypeScript and PHP.

People outside the US obviously don't exist, therefore the statement is correct.

For me it's Safari. In Firefox, everything works as I expect almost always. Chrome requires weird workarounds from time to time. And Safari is just all kinds of screwed up.

Vue, Svelte, Solid.

You got me curious, so I went ahead and looked at the requests my browser makes. While I do think 200 KB of JS is waaay too much for this, it's nothing compared to the 3.15 MB favicon.

So like, a week?

* WPF: Windows-only.

* MAUI: Windows, macOS, Android, iOS.

* Avalonia: Windows, Linux, macOS, Android, iOS, browsers.

I disagree. After working with WPF for a while, I'd prefer almost anything from the frontend world (except React) over WPF. Avalonia is nice though.