Freelance developer - React Query maintainer - Occasional OSS contributor - Been putting React on servers for a decade - Father of two - Homebrewer

Stockholm
There's been some threads on fetch-on-render vs render-as-you-fetch and what has been possible and not before Suspense (and concurrent features). Some pretty advanced patterns have been possible even before, here are some that I've used. 🧵
1
1
5
First, on the server you've basically had two options, fetch everything before rendering, or render multiple times. (At least if you ignore my experiments with the custom async SSR renderers react-aldrin and react-lightyear, but those were always experiments.)
1
2
On the client though, you've been able to do things differently. Besides just fetching in components: 1. Just like on the server, you could prefetch and wait for all data before rendering the next page. This is the default mode of things like getInitialProps.
1
1
Fredrik Höglund retweeted
L F GGGG
Today Cloudflare is announcing the open sourcing of the Workers runtime under the Apache-2.0 license! cfl.re/3LWu0bV #PlatformWeek
3
4
58
Huuge news! 🎉 I'm most impressed by the 100% incrementally adoptable part, finding a good solution for that while fully embracing the future can't have been easy. Very excited to read the RFC. 👀
📣 The Next.js router is getting a major upgrade! ◆ Nested routes / layouts ◆ Client and server routing ◆ React 18 features – startTransition, Suspense ◆ Designed for Server Components ◆ 100% incrementally adoptable 🤯 Expect an RFC very soon 👀
1
5
I've been missing this feature for years now, but I'm also kind of glad Vercel waited until all the constraints of concurrent features and RSCs were more fully fleshed out. Had they introduced nested routes earlier, I bet we would be seeing (bad?) breaking changes now.
2
Fredrik Höglund retweeted
I am _thrilled_ to announce that: 🔥🔥React-Redux v8 is now LIVE!🔥🔥 This release adds compat for React 18 (including SSR support), converts our codebase to TypeScript, modernizes build output, and removes a couple rarely-used legacy APIs: github.com/reduxjs/react-red…
8
72
472
Fredrik Höglund retweeted
Great post by @mhevery. A great summary, with examples, of the challenges of building a Progressive Hydrating solution for @QwikDev as we talked about on stream last week. Even if you aren't looking for something new, few understand the problem space better.
Why Progressive Hydration is Harder than You Think builder.io/blog/why-progress…
3
8
33
I ❤️ this categorization of architectural choices for server rendered apps(/frameworks), it simplifies a complex space in a practical way and provides a great starting point. While some are uncommon, all these combinations are possible, but it gets even more complex.. 🧵
To Start: There are rendering techniques: * Static Generation * Incremental Static Generation * Streaming SSR * SSR Hydration techniques: * None * Partial * Progressive * Full And routing architecture: * Server Routed (MPA) * Hybrid (RSCs, TurboLinks) * Client Routed (SPA)
1
2
5
Traditionally it has been very tricky to refactor between these different approaches and also to mix them within a single app. This is slowly changing, which is a great thing! For this to be possible, third party libraries also needs to support a bunch of different approaches.
1
3
I admire all the work, thought and writing @RyanCarniato has been putting into this space for a long time, I'm learning a lot by following him. I also admire all the thought and work the React team has been putting into this, also for a long time. So excited for the future!
1
Nr of times I've accidentally refreshed GitHub and lost a long reply += 1.. 🤦‍♂️
2
6
Fredrik Höglund retweeted
There is a lot of confusion around hydration in JS Frameworks. Let's look at the different approaches. "Why Efficient Hydration in JavaScript Frameworks is so Challenging" by @RyanCarniato #DEVCommunity #javascript #webdev #markojs #astrobuild #qwikdev dev.to/this-is-learning/why-…
15
96
390