[ariabuckles]

It’s really good at highly dynamic/interactive apps, such as browser versions of asana or slack, or other things where user actions are small but frequent. If you aren’t doing full page reloads and have a lot of changes, it’s much simpler than managing each individual state change in vanilla javascript.

I personally think React’s component model is much nicer than any templating system I’ve used as it supports composition as a first-class feature.

And if done well, yes you get better performance on the frontend. (If done poorly, you don’t.)

[chessturk]

> React’s component model is much nicer than any templating system

This is my feeling too. Composition and JSX beat logic in templates.

Though I've seen some pretty hairy React, I still prefer it to badly implemented template files.

[jaredcwhite]

Unfortunately, React's been around long enough now that there is legacy code that was NOT done well at all. I unfortunately inherited a project recently that was so convoluted and over-engineered, it took me like 30 minutes just to figure out how to change the logo in the top navbar. I could have done that with a Rails layout or header partial in about 30 seconds!