In reply to M Asif Rahman.

For me JSX is reason not to use React at all, this is something some people find great and others do not. So 'easy choice' is a bit misleading here unless it is framed as a personal opinion.

I'm not sure how much additional benefit there would be to go with the lib with the largest ecosystem, the benefits seem relatively minor to me?

Most of the alternatives largely follow similar conventions as React so either way we'd be picking something that is up to date. The whole purpose of the exercise is to use a tool that makes building interfaces easier and better. I haven't seen anyone expand on how React's larger ecosystem makes it better suited on that front, but maybe someone can add some thoughts about that?

Just as a general observation I've noticed no one explain why exactly React would be a special fit for WordPress's own particular needs, it seems to boil down to 'it's the most popular' and 'it's what we use at work'. There doesn't seem to be a wholly superior technical reason why React would solve problems in core better than other approaches, or why it's worth the effort of to impose additional tooling requirements, or why its worth dismissing concerns around the higher barriers to entry for newcomers, or why its worth overlooking the license factor or why it's worth affiliating with a corporation that is hostile to the open web.