For a static website with a few pages, you wouldn't need to. But for more complex apps, that's where the pay off is. A brief example: In one of our apps, we needed various select menu behaviors. Sometimes it would accept normal attributes (strings for values). Sometimes arbitrary objects having a toString method. Sometimes it needed to load data. Sometimes it needed to load data given only a model name, and know how to page it. In react, I was able to do this with a single base select component, with a few wrappers (decorators) to add in the various behaviors. All encapsulated, and abstracted behind a relatively simple interface. With honestly not that much more code than the example in this tutorial. And it all felt natural -- like I was just writing javascript. Thats the good side to React.