I won&#x27;t make an argument for Angular or Flux&#x2F;Redux because those are very opiniated frameworks that might be overkill or simply not at all how you want to go about your app&#x27;s architecture.<p>But React is about the view. You can&#x27;t possibly be convinced that manually traversing the dom is just as easy and expressive as using JSX. Even in the simplest of interactive (as in you need Javascript) components or pages.<p>React&#x27;s concept and syntax is super easy to understand and perfect for modularizing the components of your app. The real problem IMHO is the tool chain. That&#x27;s what drives developers unfamiliar with the ecosystem away. And of course the fact that it seems to change all the time. The first time I looked at React they rolled their own transpiler. Now  Babel is the recommended way to go.<p>According to the tutorial page you should either use browserify or webpack. You don&#x27;t have to - but without them stuff gets messy pretty quick. Of course if you pick one of these up you also have to learn how to use them and you will want plugin A, B and C to get to your simple Hello, World React App in the first place.<p>So yeah. That&#x27;s why it&#x27;s so easy to step away from that thinking why don&#x27;t I just simply roll my own framework.