phil

🌷💀⏳

teleyinex.eth ▫️

teleyinex.lens ▫️

teleyine.x ▫️

daniellombrana.es  ▫️

@astaralabs ▫️

@obeygiant ▫️

@scifabric ▫️

dev

I'll unpack the Deno thinking in another cast perhaps - (probably requires a little more thought and decent unpack) but the thrust of it is more around anchoring myself to  "standards" or "quasi-standards" (longer time horizon, and subjective measure on what "standards" are import).

To me, long term, it's less about Node, or Deno, or Bun (et al.) rather ESM as the long-term "continuity thread".   And the bet that, from all of the language fashions coming over the decades) JS/ESM is one long term constant we can bet on.

When it comes to things like "runtimes" though, that can get emotional and religious, so to be sure - this is just <me> ("one guys finger in the wind") taking educated stabs the macro trends on all this.  JS we get for at least the next 50 years (lindy), runtimes less so...but still long horizon...& UI/Editor/Input mechanics far more choppy and quick moving volatility.

Below my working notes. 
Thanks the prompt, need to collect my thoughts on all this as I go Daniel 🙇🏻‍♀️ 

(WIP)

WIP (thoughts): Standards ← Runtimes ← Editors

yeoro.eth → db.team → /slc → SuperBenefitDAO, All in For Sport → "purpose aligned networks of small autonomous teams”

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>