New React docs pretend SPAs don't exist anymore

#1

Post by matijash » Fri, Mar 17, 2023, 7:41 PM UTC

New React docs pretend SPAs don't exist anymore
wasp-lang.dev

Re: New React docs pretend SPAs don't exist anymore

#2

Post by jollyllama » Fri, Mar 17, 2023, 7:56 PM UTC

So they're trying to corrupt the meaning of "framework" to mean only "full stack framework"

Re: New React docs pretend SPAs don't exist anymore

#3

Post by matijash » Fri, Mar 17, 2023, 8:05 PM UTC

jollyllama wrote: post #2

So they're trying to corrupt the meaning of "framework" to mean only "full stack framework"

yeah in a way. react gets closer to being synonymous with next/remix rather than viewed as a separate, standalone library.

Re: New React docs pretend SPAs don't exist anymore

#4

Post by riidom » Fri, Mar 17, 2023, 10:55 PM UTC

Wasp is a pretty interesting project. Actually waiting until they are not react-only (if that will ever happen).

Re: New React docs pretend SPAs don't exist anymore

#5

Post by canadiantim » Fri, Mar 17, 2023, 10:59 PM UTC

matijash wrote: post #3

jollyllama wrote: post #2

So they're trying to corrupt the meaning of "framework" to mean only "full stack framework"

yeah in a way. react gets closer to being synonymous with next/remix rather than viewed as a separate, standalone library.

too much commitment for me

Re: New React docs pretend SPAs don't exist anymore

#6

Post by ecf » Fri, Mar 17, 2023, 11:01 PM UTC

Hype driven developers/marketers believe the only type of websites that exists are those which need indexable content for SEO purposes. More news at 11

Re: New React docs pretend SPAs don't exist anymore

#7

Post by [deleted] » Fri, Mar 17, 2023, 11:02 PM UTC

[deleted]

Re: New React docs pretend SPAs don't exist anymore

#8

Post by jonplackett » Fri, Mar 17, 2023, 11:04 PM UTC

I think to sway the only benefit of Next.js is DEO is underselling how useful it is.

Sure SEO is important for most people anyway, but having multiple pages that load instantly rather than having to wait for a server call is also pretty handy. Plus auth working better.

I don’t see why next wouldn’t be the default and react now the outlier.

Re: New React docs pretend SPAs don't exist anymore

#9

Post by fabian2k » Fri, Mar 17, 2023, 11:10 PM UTC

As far as I understand you can use these frameworks to write SPAs as well. I have no idea how well supported that use case is in the end.

I find the idea that you want to handle data fetching and routing in a framework to be reasonably convincing. There are advantages here, and it's easy to get into a bit of a mess if you just fetch data in each component.

The part that has stopped me from looking at the frameworks until now is that they add a lot of parts I don't need, and the documentation seems to be focused on the SSR part. And then there are React server side components, which is another new concept I need to understand. Maybe the frameworks are a good fit for my SPA use cases, but it'll take quite a bit of time to find out if that is true.

Re: New React docs pretend SPAs don't exist anymore

#10

Post by bryik » Fri, Mar 17, 2023, 11:15 PM UTC

I don't think that's a fair characterization of the "Start a New React Project" page [0]. Next.js is the first option listed and is described as a way to "create React apps of any size—from a mostly static blog to a complex dynamic application."

This reads to me like "Next.js can do SPAs (like CRA) plus static sites and SSR". Next.js' site even says "The core of Next.js has been designed to enable starting as a static site (or Single-Page Application)" [1].

0 - https://react.dev/learn/start-a-new-react-project

1 - https://nextjs.org/docs/advanced-features/static-html-export