[tyingq]

I suspect part of the rub is that with react being only the 'V' in MVC, stand-alone tutorials leave you with only part of the picture.

And, of course, people are choosing different paths to fill in the rest of the stack. All of which pull your specific 'style' of using react in slightly different directions.

[dcwca]

You're halfway there, because React is the V but there's no MVC. That design pattern isn't common in the ecosystem, and instead a functional, unidirectional design pattern called Flux is a better fit.

Searching for MVC trips a lot of developers up.

[tyingq]

>>and instead a functional, unidirectional design pattern called Flux is a better fit.

And how many different frameworks are in common use to implement that pattern? :)

Edit: Also notable the the 'V' in MVC line comes from React's home page.

[vinhboy]

I tried React about a year ago and this is how I felt. It was hard to understand how to incorporate React into an existing framework (Rails), because JSX was odd and I felt like I had to rewrite/rethink everything "V" related.