4 ms·
Currently that's the case, but I'd say React is a very good candidate for good component-based solutions; they're just not here yet. One of the reasons I've se
by mercer 11y ago
Currently that's the case, but I'd say React is a very good candidate for good component-based solutions; they're just not here yet.
One of the reasons I've seriously been considering React for even a lot of back-end stuff is that it'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, and reuse the component in other projects.
Granted, for styling there's still no solution that I consider optimal, but the advantages might be worth the 'impurity' of it all. And solutions are being worked on.
And granted, there are other initiatives like Web Components that are hopeful.
But already now React is a great option if you want to create 'independent' and re-usable components. I think it'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 'unification' across platforms.
That's assuming we won't abandon React en masse and switch to another even cooler solution in a few years, though :-/.