Ryan Dahl - Node, Deno, and JSR The Modern JavaScript Registry

This week we have Ryan Dahl, the creator of Node and Node. We talk about the road that led from Node to Deno and what he wants to do differently. We also talk about the new javascript registry, JSR, and how they hope to make a runtime agnostic town square.
github.com/ry
/ rough__sea
deno.com
Episode sponsored By Clerk (clerk.com)
Become a paid subscriber our patreon, spotify, or apple podcasts for the full episode.
/ devtoolsfm
podcasters.spotify.com/pod/sh...
podcasts.apple.com/us/podcast...
/ @devtoolsfm
00:00:22 Intro
00:01:34 From Node to Deno
00:06:50 Deno vs. Node: Philosophies, Features, and Ecosystem
00:08:43 Ad
00:10:18 Deno v Node: Part 2
00:19:07 JSR: A New Javascript Registry
00:34:34 The Evolution of JavaScript Runtimes and the Role of WinterCG
00:38:24 Deno Deploy: Simplifying Cloud Functions and State Management
00:45:37 Sub Hosting and the Future of Serverless Computing

[@PaulSebastianM]

I hear a lot of people online saying that Deno is really nicely designed compared to even other newer runtimes like Bun and they simply love using Deno because of how well thought out it is and how modern it feels compared to the older Node ecosystem.

[@fasolplanetarium]

Nowadays with Bun et al, new developers really don't appreciate how groundbreaking and novel Nodejs was. Not only was it the first truly viable server-side runtime for JavaScript, but it was built on the Unix philosophy and married two worlds of software together. I highly recommend folks go and watch Ryan's first presentation of Node (it's on YT). Great ep, so pleased you guys had him on!

[@AndersonSilvaMMA]

Finally!

[@OliverPlummer905]

🙌🙌

[@user-of6ls2ng5l]

Bun

[@okerror1451]

Man. You gotta stop. Bun is fast sure. But it is not the right direction to go. I doesn't have a cohesive plan. Stuff just breaks.. the whole ecosystem around Bun is exactly like what Bun is doing... chaotic and not really very good. And for the speed... it's not really that important at these speeds anymore.

[@user-of6ls2ng5l]

@@okerror1451 LOL

[@UliTroyo]

As a fan of Bun, I find this annoying. To me, Bun is a drop-in replacement for Node in front-end tooling, while Deno is a more cohesive development platform. I use Bun for scripting and prototyping, but I'd feel more comfortable deploying Deno in production, if I had that use-case. (Deno is still my dev REPL for JS, and my JS/TS formatter.)