react.dev VS Gatsby

I mentioned this upthread, but the "official" deprecation notice is this comment from Dan Abramov in a GitHub issue: https://github.com/reactjs/react.dev/pull/5487#issuecomment-...

That has resulted in some interesting github questions before although... it's nothing compared to Java

I found the docs confusing too. Thanks for the quotes; I went ahead and filed an issue here to hopefully get some clarity: https://github.com/reactjs/react.dev/issues/6123

Not a huge thing especially if this is used for learning, but create react app is not the best for starting new react apps. I don't think you need to change anything right now here, but he is some context. If you end up starting a new project, I'd recommend VITE

Also see https://github.com/reactjs/react.dev/issues/3896 and various online articles explaining it.

Then there's this crazy function https://github.com/reactjs/react.dev/issues/3896

Here’s a nice (and quite long) discussion about CRA and Vite, and for those who don’t want to read it all, here’s a comment from Dan Abramov regarding why CRA was created, what is it trying to solve, today’s challenges and its future.

Thank-you for reading, I hope you found this useful! Congratulations to the React team, they have done a great job with the docs. I know they are looking for feedback through their survey and issue tracker, but I’d also love to hear your thoughts on the new docs and let me know what your favourite features are in the comments below 👇

I would advise against using create-react-app in 2023. It still lives in the old docs because those won’t be updated, but the new docs have completely removed the recommendation of create-react-app. New Docs Discussion on downsides

The first time I started building static websites is when I discovered Gatsby. I built several projects using Gatsby and hosted it on Netlify free tier. It felt like a really robust architecture and I loved that it was free.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.