I’ve spent the last 6 weeks rebuilding the Crossfader website in React.js (nb: the new version isn’t live as of me writing this…), as well using it to build a couple of small things in my free time. I wanted to write down my thoughts on the framework now, and see how they compare after I’ve been using it for a few more months.
One thing I should say before diving in, is that I’ve been doing exclusively backend development since the end of 2013. These past few weeks have been my first baby steps back into the world of client-side development. It’s weird, but I don’t hate it as much as I used to.
- There is actual support for writing and running tests, thanks to jest.js. Ruby makes test-first programming a no brainer, and as a result, I’m skeptical of any code that doesn’t have tests. Things have come a long way on that front, and React makes it only a little painful to write tests, which I love.
- Most React.js components that I’ve written are actually reusable. The pass-props-to-children approach makes for easy to reason about components, that aren’t very hard to generalize out for use in other places.
The Not So Good
Overall, I’m happy with what I’ve been able to accomplish with React so far. It’s definitely a step in the right direction as far as front end UI frameworks go.