4 ms·
3 things: 1. Much of it reads as"are you taking this approach? yes? don't take this approach. no? take this approach." 2. There are also a couple of flowchart
by grumblestumble 11y ago
3 things:
1. Much of it reads as"are you taking this approach? yes? don't take this approach. no? take this approach."
2. There are also a couple of flowchart errors ("are you working on a production app" appears twice for no reason).
3. The main reason React makes me sad is the need for excruciating flowcharts like this.
As a result, the entire thing comes across as self-parody. For context, I'm a developer who works on a large enterprise app with a full build toolchain (npm, babel, webpack, sass, etc ad infinitum).
- danneu 11y agoIf you work with such a large build chain, how did you not realize that the flowchart is really about tooling complexity in the javascript ecosystem, in general? Also, the "are you working on a production app?" has two nodes so that it can model the fork into {yes bundle, no bundle}, common in flowcharts.
- danabramov 11y agoIf you take a close look at both flows you will see that point 1 and point 2 actually explain each other. :-) If you use React in production and don’t use a bundler, you should. If you don’t use React in production and do use a bundler, perhaps you shouldn’t because it will distract you from learning process. Does that help? The “need” for flowcharts like this comes from lots of misleading information on the internet about React, not from React itself. Thank you for your comments!