4 ms·

Smallish parts of JS (React, Vue, ...) sprinkled into your website for interactivity. I use it with AstroJS: https://docs.astro.build/en/concepts/islands/ https

Smallish parts of JS (React, Vue, ...) sprinkled into your website for interactivity. I use it with AstroJS: https://docs.astro.build/en/concepts/islands/ https://docs.astro.build/en/concepts/islands/

ehnto 2y ago
I straddle the fence here, I think we jump down people's throats a bit too quickly when it comes to putting names on their new library. But I do also wish we'd stop reinventing things and patting ourselves on the back in other cases. Eg we are definitely working backwards from SPAs now. "JavaScript islands" were how we got to SPA frameworks in the first place. I don't have all the history and references, but anyone working in web in the late 2000s and 2010s can attest to how progressively adding in javascript on server side rendered HTML was already happening, even componentizing the server side code with CSS and JS packaged up was very common. "The term “component island” was first coined by Etsy’s frontend architect Katie Sylor-Miller in 2019. This idea was then expanded on and documented in this post by Preact creator Jason Miller on August 11, 2020." My only gripe, is that this leads the ready on an alternate history of how we got here.
- themgt 2y ago
  The general idea of an “Islands” architecture is deceptively simple: render HTML pages on the server, and inject placeholders or slots around highly dynamic regions […] that can then be “hydrated” on the client into small self-contained widgets, reusing their server-rendered initial HTML. cryogenic lab tech: Welcome to the world of tomorrow!
  - jbverschoor 2y ago
    portlets
    - robertlagrant 2y ago
      Portlets! I see I'm not the only member here of this exclusive club.
addandsubtract 2y ago
I started out using React in "islands" almost 10 years ago. The server rendered page would have React components attached to the interactive parts of the page. Fascinating that we're coming full circle to that. Hopefully with better state management and interoperability.

ehnto 2y ago

I straddle the fence here, I think we jump down people's throats a bit too quickly when it comes to putting names on their new library. But I do also wish we'd stop reinventing things and patting ourselves on the back in other cases. Eg we are definitely working backwards from SPAs now. "JavaScript islands" were how we got to SPA frameworks in the first place. I don't have all the history and references, but anyone working in web in the late 2000s and 2010s can attest to how progressively adding in javascript on server side rendered HTML was already happening, even componentizing the server side code with CSS and JS packaged up was very common. "The term “component island” was first coined by Etsy’s frontend architect Katie Sylor-Miller in 2019. This idea was then expanded on and documented in this post by Preact creator Jason Miller on August 11, 2020." My only gripe, is that this leads the ready on an alternate history of how we got here.

themgt 2y ago
The general idea of an “Islands” architecture is deceptively simple: render HTML pages on the server, and inject placeholders or slots around highly dynamic regions […] that can then be “hydrated” on the client into small self-contained widgets, reusing their server-rendered initial HTML. cryogenic lab tech: Welcome to the world of tomorrow!
- jbverschoor 2y ago
  portlets
  - robertlagrant 2y ago
    Portlets! I see I'm not the only member here of this exclusive club.

addandsubtract 2y ago

I started out using React in "islands" almost 10 years ago. The server rendered page would have React components attached to the interactive parts of the page. Fascinating that we're coming full circle to that. Hopefully with better state management and interoperability.