Don't forget about all the embedded UIs (kiosks, appliances, car infotainment, industrial equipment, ...), those computers are weaker and it makes a ton of sense to use native toolkits there.

They tried to replace our Qt GUI at work in this space with a react based one, the new UI ran like utter shit comparatively, even after a lot of effort was spent on optimisation.

Also, most of the world don't use high end developer laptops. Most of the world is the developing world, where phone apps on low end Android phones reign supreme.

Just serialize and deserialize your JSON bro, so much faster and easier

Interesting, I have the exact opposite opinion, and I also have to deal with Web since 1999.

React is no innovation at all, some folks got a bit enthusiastic with Haskell reactive programming papers.

I think it is somewhat similar to how victims of domestic violence rationalize what happens to them.

No way someone really used Delphi and claims that it is faster to build UI with HTML/CSS/JS stack.

Indeed, if only they used something like OutSystems (https://www.outsystems.com/developers) as example, but that productivity doesn't come cheap.

Reactive UIs may have been made popular on the web, where they're an absolute nightmare, but native code does them better still.

Best time I ever had in a job was writing WPF applications in C# using ReactiveUI. Once we really understood the underlying model we were plugging stuff together so easily. It is a really good model, but I can't see how React is a good example of it.

Of course I had lots to complain about then, WPF had bugs, C# has a number of big problems, but it was, overall, very nice.