Post

It’s sad to see Deno being discontinued. However, I think it’s not all terrible. Deno pushed server side JS forward for everyone - Node copied many the standout features Deno had at launch in 2020, bringing them to the masses. Fetch, web sockets, web crypto, direct TypeScript execution, and more. 🫡

10 reposts234 likes

Node shipping fetch, web crypto and a permission flag is Deno's real legacy. Plenty of projects win by getting copied, and the copy is what most servers end up running.

genuinely cannot imagine node without all these anymore. what dark ages it was

Cloudflare should now put in the money to free the Javascript trademark from Oracle (If not already happened) haha

I'd love to see a community fork that keeps pushing it forward, and keeps focusing on innovation. Or, just maybe entirely new runtime variations.

Coincido en que su mayor aporte fue presionar a Node. En LATAM muchos equipos siguen en Node por inercia y soporte, y las ideas de Deno llegaron igual: fetch nativo, TypeScript directo. A veces influir vale más que ganar cuota de mercado.

I mean, Deno Deploy is the one being discontinued. Deno itself could live upon the community that would fork it and keep it alive no?

Is there even a measurable demand for this alternative runtime (as much as I like/love the idea)? As mentioned, Node.js ate/copied most of Deno's features already, and for extreme performance/small size/embedded runtime there are others, some with company support...

I'd say there is some demand. Considering the traction Bun has been gaining lately even with the full-AI rust rewrite landed in v1.4 But in the end I think it comes down to what compatibility and stability you are aiming for, and especially the DX that resonates with you

Thanks for all you did for the js ecosystem in your time there, Luca 🙏