4 ms·
I will also say encapsulating everything you just said in a single term, "islands," is a lot simpler and prettier to discuss. At least from my perspective, the
by charleszw 9mo ago
I will also say encapsulating everything you just said in a single term, "islands," is a lot simpler and prettier to discuss. At least from my perspective, the naming also makes a lot of sense. Literal islands of interactivity surrounded by an ocean of static.
- efilife 9mo agothe naming is backwards then. An island is static, an ocean is not. See how it is a buzzword up to your interpretation?
- aatd86 9mo agonow that you say it :o Should be astro lakes or something.
- mpeg 9mo agoIslands is just a catchy name I guess. I always thought the markojs terms for it made sense, but are more technical / less catchy: they called it “full page hydration” -> everything needs to be delivered as js and “component level hydration” -> islands, only specific component sub-trees need to be hydrated. Then “sub-component level hydration” would be resumability like in qwik where only events and their dependencies get serialised as client js.
- aatd86 9mo agoYeah. Well to their defense, it is probably to be understood as islands of interactivity lost in a sea of static elements. The term is definitely more evocative.
- michaelcampbell 9mo agoLike "meteoric rise". Meteors come down, not up. And yet, we all know what it means. Language is fun.