#serversiderendering — Public Fediverse posts

React SSR Framework Showdown: TanStack Start, React Router, and Next.js Under Load, by @mcollina (@platformatic):

https://blog.platformatic.dev/react-ssr-framework-benchmark-tanstack-start-react-router-nextjs

#frameworks #serversiderendering #react #tanstack #reactrouter #nextjs #comparisons #performance #metrics

Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.

#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.

3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.

🚫 No app store update required.

🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N

📄 #transcript included

#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering

Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.

#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.

3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.

🚫 No app store update required.

🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N

📄 #transcript included

#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering

Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.

#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.

3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.

🚫 No app store update required.

🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N

📄 #transcript included

#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering

Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.

#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.

3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.

🚫 No app store update required.

🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N

📄 #transcript included

#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering

Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.

#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.

3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.

🚫 No app store update required.

🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N

📄 #transcript included

#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering

How much JavaScript do you actually need to build a fully interactive web app?

Less than you think.

In the latest post in my Unpoly series I walk through the client-side capabilities that make it possible.

Also every Unpoly default is tunable, every action fires an event you can intercept, and you can trigger fragment replacement from any custom logic you like.

#WebDevelopment #Unpoly #HypermediaApps #JakartaEE #ServerSideRendering

https://zeromagic.eu/posts/unpoly-client-side-capabilities/

How much JavaScript do you actually need to build a fully interactive web app?

Less than you think.

In the latest post in my Unpoly series I walk through the client-side capabilities that make it possible.

Also every Unpoly default is tunable, every action fires an event you can intercept, and you can trigger fragment replacement from any custom logic you like.

#WebDevelopment #Unpoly #HypermediaApps #JakartaEE #ServerSideRendering

https://zeromagic.eu/posts/unpoly-client-side-capabilities/

Your React app looks beautiful. Search engines see a blank div. Here's the lightweight server-side fix that actually works in production. https://hackernoon.com/seo-best-practices-for-modern-web-apps #serversiderendering

Most internal business UIs don’t need a JavaScript framework.

They need to load fast, behave predictably, and still make sense in five years.

This article shows how to build a customer dashboard with Quarkus and Qute using server-rendered HTML and browser-native features like <dialog> and <details>.

Less tooling. Fewer moving parts. More stability.

https://www.the-main-thread.com/p/lean-business-ui-quarkus-qute-no-javascript

#Java #Quarkus #WebDevelopment #ServerSideRendering #EnterpriseSoftware

I keep seeing teams add frontend frameworks just to avoid page reloads.

HTMX offers another option.

This article shows how to build interactive UIs with Quarkus, Qute, and plain HTML.
Server-rendered. Fragment-based. No custom JavaScript.

If you’re a Java developer who prefers boring, predictable stacks, this one’s for you.

🔗 https://www.the-main-thread.com/p/htmx-quarkus-server-rendered-ui-java

#Java #Quarkus #HTMX #ServerSideRendering

Intro to Performance of React Server Components, by @adevnadia.bsky.social:

https://calendar.perfplanet.com/2025/intro-to-performance-of-react-server-components/

#introductions #performance #react #components #serversiderendering

Is Server-Side Rendering React’s Holy Grail?, by @Lowrain (@TheNewStack):

https://thenewstack.io/is-server-side-rendering-reacts-holy-grail/

#react #serversiderendering

A Guide to Understanding and Using React Server Components

https://www.writeforustech.net/2025/06/react-server-components-guide.html

Learn how React Server Components enhance performance by splitting rendering between server and client. This guide explains their benefits, use cases, and how to implement them effectively in modern web apps.

#ReactServerComponents
#ReactJS
#WebDevelopment
#FrontendPerformance
#ServerSideRendering
#ModernWebApps
#JavaScript
#ReactDevelopers
#FullStackDevelopment
#React2025

A Guide to Understanding and Using React Server Components

https://www.writeforustech.net/2025/06/react-server-components-guide.html

Learn how React Server Components enhance performance by splitting rendering between server and client. This guide explains their benefits, use cases, and how to implement them effectively in modern web apps.

#ReactServerComponents
#ReactJS
#WebDevelopment
#FrontendPerformance
#ServerSideRendering
#ModernWebApps
#JavaScript
#ReactDevelopers
#FullStackDevelopment
#React2025

A Guide to Understanding and Using React Server Components

https://www.writeforustech.net/2025/06/react-server-components-guide.html

Learn how React Server Components enhance performance by splitting rendering between server and client. This guide explains their benefits, use cases, and how to implement them effectively in modern web apps.

#ReactServerComponents
#ReactJS
#WebDevelopment
#FrontendPerformance
#ServerSideRendering
#ModernWebApps
#JavaScript
#ReactDevelopers
#FullStackDevelopment
#React2025

A Guide to Understanding and Using React Server Components

https://www.writeforustech.net/2025/06/react-server-components-guide.html

Learn how React Server Components enhance performance by splitting rendering between server and client. This guide explains their benefits, use cases, and how to implement them effectively in modern web apps.

#ReactServerComponents
#ReactJS
#WebDevelopment
#FrontendPerformance
#ServerSideRendering
#ModernWebApps
#JavaScript
#ReactDevelopers
#FullStackDevelopment
#React2025

A Guide to Understanding and Using React Server Components

https://www.writeforustech.net/2025/06/react-server-components-guide.html

Learn how React Server Components enhance performance by splitting rendering between server and client. This guide explains their benefits, use cases, and how to implement them effectively in modern web apps.

#ReactServerComponents
#ReactJS
#WebDevelopment
#FrontendPerformance
#ServerSideRendering
#ModernWebApps
#JavaScript
#ReactDevelopers
#FullStackDevelopment
#React2025

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant

SSR vs. SSG vs. CSR vs. ISR—Rendering Performances Compared, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/ssr-vs-ssg-vs-csr-vs-isr-rendering-performances-compared/

#guestposts #serversiderendering #staticsitegeneration #clientsiderendering #incrementalstaticregeneration #comparisons

SSR vs. SSG vs. CSR vs. ISR—Rendering Performances Compared, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/ssr-vs-ssg-vs-csr-vs-isr-rendering-performances-compared/

#guestposts #serversiderendering #staticsitegeneration #clientsiderendering #incrementalstaticregeneration #comparisons

SSR vs. SSG vs. CSR vs. ISR—Rendering Performances Compared, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/ssr-vs-ssg-vs-csr-vs-isr-rendering-performances-compared/

#guestposts #serversiderendering #staticsitegeneration #clientsiderendering #incrementalstaticregeneration #comparisons

SSR vs. SSG vs. CSR vs. ISR—Rendering Performances Compared, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/ssr-vs-ssg-vs-csr-vs-isr-rendering-performances-compared/

#guestposts #serversiderendering #staticsitegeneration #clientsiderendering #incrementalstaticregeneration #comparisons

SSR vs. SSG vs. CSR vs. ISR—Rendering Performances Compared, by @designerly.bsky.social:

https://frontenddogma.com/posts/2025/ssr-vs-ssg-vs-csr-vs-isr-rendering-performances-compared/

#guestposts #serversiderendering #staticsitegeneration #clientsiderendering #incrementalstaticregeneration #comparisons

SSR Deep Dive for React Developers, by @[email protected]:

https://archive.fo/G9kdE

#deepdives #serversiderendering #react #javascript

I think this is as far as I'll go for this sample blog-eske website

This is a classic'ish website with aspnet and F# server-side rendering, almost no JS, no HTMX, streamed HTML and, if you see it on a chromium browser you won't even notice page reloads!

https://github.com/AngelMunoz/Openapo

You can see the live thing here: https://openapo.fly.dev/posts/Server+Sent+Events+with+Saturn+and+F%7e%7e_2024-10-27-37

#fsharp #dotnet #aspnet #server #webdev #html #serversiderendering #backend

👩🏻‍💻👨🏻‍💻 Moderne Webentwicklung: Back to the Server!
Die Ära der klassischen Single Page Applications mit #Angular, #React und #Vue scheint sich dem Ende zuzuneigen! Doch was bedeutet der Trend zu full-stack Frameworks wie Next.js, Remix und Svelte wirklich für die Webentwicklung?
🔎 Taucht gemeinsam mit Jonas Bandi ein in die neuesten Ansätze zur Full-Stack-Webentwicklung ein an der #BaselOne24
🐸 https://lnkd.in/ggjmzerN

#WebDevelopment #FullStack #ServerSideRendering #Nextjs #Svelte

I'm continuing my series on #ServerSideRendering (with @springboot) and #AJAX.

This week, I look at @htmx_org and how it nicely complements #SpringBoot.

https://blog.frankel.ch/ajax-ssr/5/

To all the people who laughed at me for understanding and enjoying #regex

I just moved a large project from #react #vite to #Astro mostly thanks to the power of regex.

Cutting down client side JavaScript.

#astrojs #ssr #ServerSideRendering

Lol my realization today:
"I wonder if I could serialize all of the nodes, pick the async ones and rather than wait for their individual content to render, send a marker element instead, so when those async nodes finish working they can be sent via server sent events or any other means available."

Oh wait, I'm reinventing poor's man astro in F#🫠
Welp that won't stop me from trying out stuff!
It is nice to see that This kind of technology is not JS only, other ecosystems simply don't care... There's so much potential down there!


#fsharp #backend #serversiderendering #experiments #webdev #htmlrendering

@redacted @reiver @ellisgl On the other hand, I've seen a lot of websites deliberately turn off #ServerSideRendering when analytics show that a lot of visitors are using script blockers to evade interest-based ads and metering. #Quora and #Fortune are among them.

SMH every time I read about #JavaScript #frontend development:

“Thoughts On React Vs Vue Vs Everything Else In 2023”, Charles Chen (https://chrlschn.medium.com/thoughts-on-react-vs-vue-vs-everything-else-in-2023-e4e50e526049).

Via HN: https://news.ycombinator.com/item?id=36168354

#React #Vue #NextJS #Svelte #TypeScript #StaticSiteGenerators #ServerSideRendering #SSG

I wish you could switch off turbolinks or frames or whatever GitHub uses to update its pages - just give me server side rendering please!

#GitHub #Turbo #Rails #ServerSideRendering #Grumpy

Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

@slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

@slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

@slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

@slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

@slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

Lol my realization today:
"I wonder if I could serialize all of the nodes, pick the async ones and rather than wait for their individual content to render, send a marker element instead, so when those async nodes finish working they can be sent via server sent events or any other means available."

Oh wait, I'm reinventing poor's man astro in F#🫠
Welp that won't stop me from trying out stuff!
It is nice to see that This kind of technology is not JS only, other ecosystems simply don't care... There's so much potential down there!


#fsharp #backend #serversiderendering #experiments #webdev #htmlrendering

Lol my realization today:
"I wonder if I could serialize all of the nodes, pick the async ones and rather than wait for their individual content to render, send a marker element instead, so when those async nodes finish working they can be sent via server sent events or any other means available."

Oh wait, I'm reinventing poor's man astro in F#🫠
Welp that won't stop me from trying out stuff!
It is nice to see that This kind of technology is not JS only, other ecosystems simply don't care... There's so much potential down there!


#fsharp #backend #serversiderendering #experiments #webdev #htmlrendering

Lol my realization today:
"I wonder if I could serialize all of the nodes, pick the async ones and rather than wait for their individual content to render, send a marker element instead, so when those async nodes finish working they can be sent via server sent events or any other means available."

Oh wait, I'm reinventing poor's man astro in F#🫠
Welp that won't stop me from trying out stuff!
It is nice to see that This kind of technology is not JS only, other ecosystems simply don't care... There's so much potential down there!


#fsharp #backend #serversiderendering #experiments #webdev #htmlrendering

Lol my realization today:
"I wonder if I could serialize all of the nodes, pick the async ones and rather than wait for their individual content to render, send a marker element instead, so when those async nodes finish working they can be sent via server sent events or any other means available."

Oh wait, I'm reinventing poor's man astro in F#🫠
Welp that won't stop me from trying out stuff!
It is nice to see that This kind of technology is not JS only, other ecosystems simply don't care... There's so much potential down there!


#fsharp #backend #serversiderendering #experiments #webdev #htmlrendering

SSR Deep Dive for React Developers, by @[email protected]:

https://archive.fo/G9kdE

#deepdives #serversiderendering #react #javascript

SSR Deep Dive for React Developers, by @[email protected]:

https://archive.fo/G9kdE

#deepdives #serversiderendering #react #javascript

SSR Deep Dive for React Developers, by @[email protected]:

https://archive.fo/G9kdE

#deepdives #serversiderendering #react #javascript

SSR Deep Dive for React Developers, by @[email protected]:

https://archive.fo/G9kdE

#deepdives #serversiderendering #react #javascript