Currently that&#x27;s the case, but I&#x27;d say React is a very good candidate for good component-based solutions; they&#x27;re just not here yet.<p>One of the reasons I&#x27;ve seriously been considering React for even a lot of back-end stuff is that it&#x27;s really easy to create an isolated component that combines markup, styling and behavior. Once done, I can simply require() the component on either the back- or front-end, or both, <i>and</i> reuse the component in other projects.<p>Granted, for styling there&#x27;s still no solution that I consider optimal, but the advantages might be worth the &#x27;impurity&#x27; of it all. And solutions are being worked on.<p>And granted, there are other initiatives like Web Components that are hopeful.<p>But already now React is a great option if you want to create &#x27;independent&#x27; and re-usable components. I think it&#x27;s just a matter of time before a proper, popular component-ecosystem arrives, and what with React Native, there might even be some degree of &#x27;unification&#x27; across platforms.<p>That&#x27;s assuming we won&#x27;t abandon React en masse and switch to another even cooler solution in a few years, though :-&#x2F;.