Post

react.dev is designed for folks who are new to React or are learning basic React concepts. While we'd love to have docs for more advanced users of React (e.g. libraries, frameworks, build tools, etc.) we don't have the resources to make that happen today.

Because react.dev's audience is new users, the recommendations are also tailored to new users. We don't want to recommend a path for new user where they may have to rewrite a significant part of their app to get a feture they figure out they need down the line

Its hard to recommend a build tool to someone new to React knowing that they might find themselves needing a different rendering strategy (e.g. CSR, SSG, SSR) per route, with data fetching included

This isn't perfect and most of the folks reading this post aren't the primary audience for this page (or react.dev) because they know the tradeoffs already and can make their own, informed decision.

0 reposts3 likes

I never really got the "let's just hide the complexity to avoid confusing the audience" argument. These new devs end up battling reduced portability due to runtime constraints from the framework, jargon overload and overall complexity, just because they might need some feature in the future? 🤷‍♂️