Deno 2 • Ryan Dahl • GOTO 2024

[@GOTO-]

Looking for books & other references mentioned in this video? Check out the video description for all the links! Want early access to videos & exclusive perks? Join our channel membership today: kzbin.info/door/s_tLP3AiwYKwdUHpltJPuAjoin Question for you: What’s your greatest takeaway from this video? Let us know in the comments! ⬇

[@jaortiiss]

21:08 - pulling npm dependencies 23:55 - percent c

[@icantchosemyname]

He is really brilliant, is this how a 10x programer looks like? 🤯 Seriously RESPECT++ to him and the team behind deno.

[@ModeratelyInsane]

Very cool. The current situation where you have to set up all the tooling (tsc/eslint/prettier) separately is very painful for someone who is new to the ecosystem. Also the absolute clusterf that is CommonJS/ESModules, even for seasoned programmers, can be tricky to navigate. This Deno approach is very compelling.

[@shellcatt]

Can't believe you decided to drop the `unpublish` function for JSR. This is essential, dude.

[@karthik-u7y4d]

yuck!! why do you need it?

[@shellcatt]

@@karthik-u7y4d To have control over my own code on a public cloud, for example?

[@karthik-u7y4d]

@@shellcatt once you publish it to a public registry, it's not your code anymore

[@shellcatt]

@@karthik-u7y4d As a proprietor, my code is signed as authored by me. The cloud only hosts a digital copy of it. Almost all cloud providers support data un-caching, especially when in accordance with EU laws. A registry is a centralised entity and should not act as an immutable distributed database.

[@unorsk]

I love the error at the end of the talk "cannot read properties of undefined". JS in a nutshell :)