Sitemap
Jeff Cunningham

Jeff Cunningham

Javascript, Books, Sports

Book Review: Fullstack React

4 min readDec 27, 2016

Update (Oct 2017): I’ve updated my thoughts on this book, as this book as evolved over the last few months. See here.

I’ve been doing Angular.js development for over 3 years now, and am ready to move on (more on that in a future post). In the fall of 2015, I spent 2–3 months working on a React project for my employer, but haven’t had a chance to do anything with React since that project. I’m more than ready to jump back in, so I thought I would start by reading some books. In the ReactJS sub-reddit, I see “recommend a good React book” posts fairly often. This post (and others in the near future) are an attempt to help answer that question.

For the first review in this series, I plan to share my reaction (no pun intended) to Fullstack React: The Complete Guide to ReactJS and Friends. One reason I chose this book is that I was already familiar with some of the authors (having read ng-book and ng2-book). Plus, it seemed to be a long book, covering a lot of topics: React, Redux, Testing, Components, Webpack, etc. In fact, the book was updated last week to include a new chapter on React Router v4. This new chapter (which I have NOT yet read), brings the page count of this book to almost 700 pages! So how much did I learn? Would I recommend it?

Get Jeff Cunningham’s stories in your inbox

Join Medium for free to get updates from this writer.

Overall, I thought the book was pretty good, but not a homerun. As I mentioned above, it covered most of the topics I was looking for (I wouldn’t mind seeing a couple of appendixes to cover Typescript and Immutable.js, seamless-immutable or Flow) and I learned something (lots of somethings) from every chapter. For example, using Destructuring in Arrays and Objects, was a really neat way to create new (immutable) objects when dealing with updates to state. In fact, ES6 (and some ES7) was used throughout the book, and these were some of the most helpful sections to me. I also appreciated the application of functional programming principles, which helped reinforce my opinion that I want to continue to find ways to apply that to my current (Angular 1.5) project.

While the list of topics were good, and covered well, there were some things that could be improved. One of the most glaring is the use of React.createClass in most all of the examples. It was confusing to see ES6 being used, but not for creating components. Maybe this is still contentious in the React community? Is there still a debate about using ES6 classes to create React components? I know their has been a huge movement toward functional concepts, but surely that doesn’t mean classes can’t be used to component creation? (aside..of course, there is a more concise way to handle stateless components…I’m referring to Container/Smart components above). As a weird side-effect, seeing React.createClass made we wonder if the other parts of the book were outdated and not using current best practices? The more I read, the more I came to believe the book was up to date on best practices. But I guess as I read other books, I’ll find out if that is really true.

Two other things also bothered me: there were times when I felt the teaching focus of the book leaned more toward learning the example app, instead of learning the core React concepts in the chapter. I find that a common problem in books with a really high page count. Don’t get me wrong, the book does teach the React fundamentals rather well. There were just times when I felt the teaching was lost in all the examples. And the last nitpick was that the book kept all code in a single file in most (all, except for the Webpack chapter I believe) chapters. I would have liked some teaching and discussion on how to structure an app. Yes, I’ve worked in React before, and was even doing component based Angular 1.x 2 years ago…so I have a pretty good grasp on how to structure large, component based apps. But I still would have liked to see it covered in the book (unless I totally missed it. I did not read the testing chapters, the GraphQL chapters, or the new router chapter, but I believe I read everything else).

Despite the critiques above, I still think Fullstack React is worth reading if you are new to React and the supporting libraries this book covers. I’m not sure it’s the BEST book, but you will learn what you need to be productive.

NEXT: Tonight I bought a react book from Leanpub: The Road to Learn React. At 103 pages (currently), it is a LOT shorter then Fullstack React. It also has a much narrower focus…covering only core React. I’ve read good things about the author, so I’m looking forward to reading it!

--

--