What I Discovered When I Compared React and NextJS for Astro 5's Server Islands

Astro 5's server islands make it easy to stream slow loading components to the client. You can use Astro components, or React, Vue, Svelte, Solid, or any other framework with adapters to Astro.

👉 VS Code theme and font? Night Wolf [black] and Operator Mono
👉 Terminal Theme and font? oh-my-posh with custome prompt and SpaceMono NF

00:00 Introduction
00:28 Trying out server:defer
01:30 Adding a fallback
02:20 How it works
04:15 How NextJS/React does it
07:03 It’s not partial pre-rendering
09:04 Server islands for React
10:19 Outroduction

[samuelhulla]

Hey one thing worth mentioning that I felt was omitted when comparing next to Astro about having data ready for server components without Suspense for SEO, you technically still can have this ready by doing a top level await call at the top of .Astro file which does fetch data at build time and serves them in a SEO optimized way. Not the same as server components but still felt worth mentioning for completeness of the comparison

[seannewell]

Really well done Jack, looking at the nuances of each approach is really import ant for making and backing up decisions. Not to mention understanding when things break!

[inderjotsingh]

I watched Theo's video where we was explaining that in case of PPR you need computational unit Lamdba that is responsible for first serving the cache skeleton from the CDN and parallelly initiating request for Dynamic Data . However in case you Astro no lambda is required request will go directly hit the CDN and we will get the static shell without any lambda cold starts and once the shell is received in the client it initiates request for the Dynamic data to the server . So, for the complete paint PPR takes less time but we will get static shell first in case of Astro . Theoretically

[Cahnisama]

Next wants to lock you win on Vercel with Partial Pre Rendering. Meanwhile my boi Astro is here killing it with islands!

[webdev]

So from an SEO perspective, is it better to use Next's PPR ?

Astro server islands look a lot like client islands, at least from an SEO perspective.

[PraiseYeezus]

Can you clarify what you mean by PPR 'caching' the content from a CMS? So even though the Header content is technically dynamic since you're fetching it, you're saying that during build you can still fetch the data and make it static? That just sounds like generateStaticParams, isn't it?

[beyourahi]

is Astro Server Islands the same as Next.js Partial Prerendering (PPR)?

[waleedsharif]

Could you possibly talk about: which one to use for programming ChatGPT 4o or Open AI o1 ?

[SrikrishnaGumma]

Does this work with Nextjs app deployed in EKS? My understanding is EKS doesn’t stream

[matttamal]

Does anyone actually get to use these new fun things at their job? It's hard to justify to a PM, but it all looks so interesting

[ChronicleContent]

do LLMs suggest and code like these things?

[igortalic]

Astro maybe a little bit inspired by HTMX :)

[sevilaytemiz]

Hi Mr Herringten, I'm not a senior yet, but learned many things from you. I want to ask you, how many people say that they are senior but in reality they are not.

[rucklerful]

hey Jack, sorry for asking a non related question but what is youre default method of autogenerating youtube timestamps?

[KETNES]

PS i'm totally team astro, but also re-tried fresh after deno2.0, and got to say there is a lot to like too.
plenty overlap with server first and islands, but fresh has commited to preact.
and partials are a cool explicit alternative to view Transitions before those are stable.

You've covered fresh before, but i think its newly relevant with deno2.0, i'd love to use it for a larger project soon, wonder what the downsides / tricky parts here would be. partials feel like an easy way to do a bit of htmx style updates