🗣 This was originally posted as a reply over at Dave’s blog. Unfortunately Disqus — the commenting system Dave uses — thinks it’s spam, so I’m posting it here as a full post instead.
In his blogpost The React is “just” JavaScript Myth, Dave Rupert said this:
React shows up on the scene with Babel, Webpack, and JSX (which each have their own learning curve) then quickly branches out into technologies like Redux, React-Router, Immutable.js, Axios, Jest, Next.js, Create-React-App, GraphQL, and whatever weird plugin you need for your app.
As a JavaScript developer (who happens to be writing mostly React (Native) these days) I’d like to counter that though …
Babel + Webpack + JSX: Yes, those are the basics. To run a train you need a locomotive, tracks, and a power source.
Although … thanks to things like create-react-app (CRA) you can start coding out-of-the-box as it has a babel-webpack thing set up for you. Even though highly interesting you don’t really need to know the inner workings of Babel nor Webpack when starting out with React.
As for JSX: JSX syntax essentially compiles down to functions. You don’t really need JSX, but if you wouldn’t use it your code would grow exponentially (<b>vs. React.createElement('b', { children, … })). If you know HTML, JSX can be learnt quite easily.
As for the rest of the things Dave mentions: these are not mandatory. Don’t let this list of fast- and ever-changing technologies overwhelm you, as you can easily create a React app without ‘m:
- Redux — Even the author of Redux himself says you might not need it. (It is nice to work with though 😉)
- React-Router — You can perfectly use different pages if you want. Additionally you don’t need a router when refactoring one or two components from your site to React implementations.
- Immutable.js — I’ve written quite a lot of React apps by now and have used it only once so far.
- Axios — You can use ES’ built-in
fetchinstead. No need to learn another library 😉 - Jest — Only if you want to write tests
- Next.js — Never used it
- CRA — Never used it.
- GraphQL — Never used it (but I am really interested in it).
Of course, as your code and knowledge evolves, you most likely will start using one / a few / all of those 😉
The one thing Dave hasn’t mentioned (by name) in his post is ES2015. To me that was the biggest hurdle to take when starting out with React.
Reading Dave’s post I think his — and many others’ — gripe with React comes from exactly this. It’s easy to confuse React-specifics with ES2015-specifics since React uses a lot of the new ES language features.
Take Array.prototype.map for example (which Dave mentions): that’s an ES feature and has nothing to do with React itself. There’s even an article dedicated to this distinction: “Learning React: Is This ES6 or React?”
Once one embraces these new ES features — which I have a full presentation about — and uses ‘m more often one will start loving them … I know I have 😊
TL;DR To start with React, learning ES2015 is essential. Sprinkle some JSX on top and you’re good to go. It’s ES2015 that’s the hardest part to learn. React itself builds on top of these language features. So yes, React really is “Just JavaScript”.
💡 This post first appeared on my blog bram.us. You can follow my blog via RSS, Twitter, and Facebook.
