3 ms·
It might seem chaotic to you, but the docs change has been a long time coming, and isn't a surprise to anybody. > Is this just a really bad time for React The
by schwartzworld 4y ago
It might seem chaotic to you, but the docs change has been a long time coming, and isn't a surprise to anybody.
> Is this just a really bad time for React
There are some concepts you may struggle with. That's to be expected.
But the new docs don't represent negative change. The old docs were not representative of how most react is written today. That was really confusing for newcomers. There's nothing "wrong" with doing it the old way, but most jobs that use React are going to require you to work with hooks in some capacity.
- KyeRussell 4y agoHow deep in the React ecosystem do you have to be to NOT see that the problems OP is describing are not inherent in change, but rather Meta deprioritising public / open-source React? You wouldn’t see this shit otherwise. Especially with Meta’s resources, there were MUCH better ways to handle React’s documentation situation. The JS community, but especially React, just happens to set the bar on the floor as far as end user communication goes, compared to other open-source projects, say…Django, with like…two paid staff and a bunch of volunteers. This isn’t just the cost of progress. It’s laziness.
- xcrunner529 4y ago[dead]