React is going to rewrite the documents

The debate about who is the better choice, Vue or React, never seems to stop. But on one point, fans on both sides seem to agree on something rare:

The Vue file is much better than the React file.

The React developers explained that Vue was developed by Chinese people, so the document is more suitable for Chinese people to read.

But based on #3308, it seems like React developers around the world are struggling to document. So much so that in the issue, React Core Team member rachelnabors broke down and said,

“To make up for the lack of official documentation, eager developers have created their own React tutorials. We want the official document to be the only one with you from the time you write your first React component to the end of your career.”

As Hooks become more recognized, the existing document is built around ClassComponent, with Hooks as a separate section.

For these reasons, the React team decided to rewrite the document.

The nature of the React documentation

Is the difference between documents really just because “the documents written by Chinese people are better for Chinese people to read”? Obviously not.

To understand the document differences, you need to talk about the framework differences.

Vue is developed based on a “template language” with a higher level of abstraction. His documentation is essentially an introduction to the syntax of a “template language.”

Just memorize the grammar you need.

React is less abstract and uses JS directly (JSX is just syntax sugar).

React takes a long time to explain how various data streams and design patterns are used in React, compared to Vue syntax.

To solve component reuse, React has HOC, render props, composite patterns, and many other concepts.

This is where it gets hard.

What changes have been made to the new document

Knowing the crux of the problem, let’s see what changes will be made in the new document.

  1. In order toHooksIs used throughout the document

By not using ClassComponent as an example, it also shows that Hooks have gained community acceptance as de facto development standards.

  1. “Glossary and concept explanation” for programmers.

React, including Redux, is fond (modified, very fond) of using theories and concepts to guide their work (e.g. the algebraic effects on Hooks).

This makes a lot of front end side exclaim “tall on” while wailing “don’t understand”.

To this end, the new document will add a lot of terms and concepts to explain.

  1. More sample diagrams, online demo, integrationDev-toolsandlint.

Illustrated and easy to understand, online demo is convenient to learn while practicing. It’s a two-pronged, well-intentioned approach.

And the new document was written by Dan Abramov himself. Front end of the top net red horse, the importance of visible spot.

When will you see it

It smells so good. When can I see it? The official answer: early 2021.

The current version of the document is archived and the new version is not modified based on the current version of the document.

If you can’t wait, there are official Hooks based documentation for the current version.