3 ms·
> You can then optionally send less HTML by just sending the parts that you expect to have actually changed, your "islands". And then you end up with modern SS
by LudwigNagasena 2y ago
> You can then optionally send less HTML by just sending the parts that you expect to have actually changed, your "islands".
And then you end up with modern SSR frameworks that do the bookkeeping for you.
- Imustaskforhelp 2y agoyes but mostly the island architecture is only dominant in the javascript world we can basically get the benefits of spa without having to learn js / use minimal js using htmx in some sense https://github.com/donseba/go-htmx https://github.com/donseba/go-htmx check this out
- dingnuts 2y agoIf you render HTML on the client you still have to render a transport format (usually JSON) on the server side. Sending HTML just lets you skip the transport format and the client side rendering.
- LudwigNagasena 2y agoAnd letting your framework do the bookkeeping for you lets you skip the whole issue. I don't know the exact specification of React Server Component Payload, but I know that it somehow changes stuff on the client-side when the client interacts with the server. (It sends something like `["$","p",null,{"children":["a child","another child"]}]`)
- traverseda 2y agoIt's still one server side template, you just render different parts depending on what is calling it. By default render a full page, if you want to get precious about a few dozen KB from sending a full page over the wire you can toggle some blocks off.