React (Facebook's JS UI Library): Yay or Nay?

programming web dev
1

We use Crashlytics and I noticed a blog post on their moving from Backbone (which we also use) to React: Why We Are Converting to React.

There seems to be a lot of react talk as of late, but I’m also seeing some hate (rhymes!): React Is A Terrible Idea. There, the author says:

React seems to have bumped Angular from the top of the hippest-framework mountain. This is unfortunate, because both of these frameworks are bad for your application’s health. They’re also bad for the entire software industry.

He goes on to recommend using Web components instead.

Has anyone been using React? What do you think? And if not, does it look like its something you’d like to use?

2

I have been fiddling with React quite a bit for the past few weeks, and I like it a lot. While I don’t have a real use outside of a “Look, I’m learning something cool!” case, it seems to provide some really nice functionality for creating single page apps. Creating navigation between sections or pages is always a pain, and this does it with a bit more glitz than Angular.

:stuck_out_tongue:

3

Sounds like a Yay for React!

I haven’t really used it myself. I took a very short (too short to be completed) lab where we were attempting to convert something using, I think Backbone, to React. Didn’t get a whole lot out of that, at least not enough to really have an opinion on it.