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.

the naming is backwards then. An island is static, an ocean is not. See how it is a buzzword up to your interpretation?

now that you say it :o

Should be astro lakes or something.

Islands 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.

Yeah. 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.

Like "meteoric rise". Meteors come down, not up.

And yet, we all know what it means. Language is fun.

See also the Slang shader language, it's a pretty recent development! https://shader-slang.org

Want to submit to HN and email us ([email protected]) so we can put it in the SCP? (https://news.ycombinator.com/item?id=26998308)

That omelette does look delicious though.

Yes, I constantly use this pattern in C++/JavaScript, although I haven't tested how performant it is in the former (what does the compiler even do with such an expression?)

At least in simple cases the compiler will just inline the closure, as if it never existed. There shouldn't be any measurable overhead.