You could be right and I may not have understood. I haven’t learned either, so may be wrong but my impression is that there’s not that much difference in learning one or the other. I think that the same concepts, components etc apply to both (so I went to the React docs to understand how I might customise React-static), but React-static generates faster code by automating things that would take more work to achieve in React, and I would guess comes with some restrictions. But that is mostly guesswork.
Best to ask the React community, and Tanner in particular for a definitive answer.
I’ve asked @SleeplessByte if he might comment, and found this:
React vs React-Static: What are the differences?
What is React-Static? A progressive static-site framework for React . React-Static is a next-gen static site generator for React. Finally, you can build a website like you do any other React App. There’s no special CMS, query language, or crazy lifecycle hooks. Just good old React producing an amazing SEO-ready, user experience driven, progressively enhanced website. The effort is minimal, but the benefits are not!.
And this intro from Tanner was one of the first things I read and very helpful. It includes:
Introducing React Static !
A progressive static-site framework for React, designed to deliver an amazing experience for your users and developers alike, without compromising React in any way. It’s insanely fast, SEO-ready, and is the most React-friendly static-site library on the planet.
Let’s get to it.
How is it different?
Contrary to most other static site generator for react, React-Static is very direct with how data flows from its source to a route. Not only does this provide a convenient abstraction point for managing all of your static data, but by keeping the data pipelining and react templating as separate as possible, your site can be built as a “function of state” with only a single pass of SSR!