[hombre_fatal]

Without trying new things, you get stuck with, say, UIKit + CoreData which make me miss React every second I'm building an iOS app. All the KVO stuff that make it hard to actually reason about state changes.

Of course React, like any library/framework, is going to have its own idiosyncrasies. That isn't the question. The question is if it's still better than alternatives, and people clearly seem to think so. My first React app I ever made years ago still works on the latest React, seems pretty stable as far as the web client ecosystem goes.

Client development isn't trivial on any platform, btw. But I think we have it pretty damn good on the web, relatively.

[pjmlp]

We will only have it damn good on the web when it is as easy as doing RAD apps in Delphi, or using Blend to design UI layouts.

I see a good possibility with WebComponents, which React seems to be the only framework not going for them.

[crooked-v]

To me, Web Components are bound by the fundamental anti-pattern of having to globally register unique tag names. Didn't people already learn the problems with doing this from Angular 1?

[pjmlp]

Because the best practice is to prefix them anyway, following up on XML namespaces?

[crooked-v]

The contrast I mean to emphasize is React, where the tag you use is either an actual var declaration or a string placeholder for a browser (or other environment) built-in.