I'm surprised so few people have watched it so far. A speech from Ryan Dahl, the creator of NodeJS? And 8 hours later, mine is the first comment? Where are all the devs at?
Because good enough is better than better in the real world and in the real world people have built entire careers on making sense of complex build systems and linting systems for organizations-it’s political per usual and it is cost prohibitive per usual.
Deno is great. 10:09 NPM/Node compatibility is a good thing, but I think Deno is compromising a lot in the way it is bringing the Node ecosystem onboard. Indeed, Deno has taken the route of polluting its clean runtime implementation with native NPM/Node compatibility, but nowadays we have JavaScript CDNs that transform NPM modules into ES modules. It would have been possible for Deno to keep its runtime pure and put the whole messy and obsolescence-ridden Node ecosystem behind a JS CDN. Deno-based software relies on the Internet on a fundamental level, so such software can always rely on JS CDNs being available at run-time. Deno could even have decided to operate its own JS/TS CDN.
I think you just saw a chart where Deno is slower but not the other chart Also in Deno 1.43 there is a performance increase, but I haven't see anyone except Deno engineer who bench it
Bun is more interested in speed than correctness. We'll see how that goes in the long run. I think both deno and bun will start eating into node's lunch, and both can exist together for different use-cases.
I'm surprised so few people have watched it so far. A speech from Ryan Dahl, the creator of NodeJS? And 8 hours later, mine is the first comment? Where are all the devs at?
Its not a music video, it will sure get its views and comments in coming days.
Or may be sensei Ryan might have left every viewer speachless.
Ofc there are other copies ruclips.net/video/LVEGRj3RZSA/видео.html
Not using Deno ;(? yet..?
@@MrFoxPro what explanation you want?
I don't understand why deno hasn't been adopted as node was.
I know, fr
Backwards compatibility with older node packages could be one reason?
Because good enough is better than better in the real world and in the real world people have built entire careers on making sense of complex build systems and linting systems for organizations-it’s political per usual and it is cost prohibitive per usual.
Deno is great. 10:09 NPM/Node compatibility is a good thing, but I think Deno is compromising a lot in the way it is bringing the Node ecosystem onboard. Indeed, Deno has taken the route of polluting its clean runtime implementation with native NPM/Node compatibility, but nowadays we have JavaScript CDNs that transform NPM modules into ES modules. It would have been possible for Deno to keep its runtime pure and put the whole messy and obsolescence-ridden Node ecosystem behind a JS CDN. Deno-based software relies on the Internet on a fundamental level, so such software can always rely on JS CDNs being available at run-time. Deno could even have decided to operate its own JS/TS CDN.
damned if you do damned if you don't!
why Deno is slower than Node js ya? I saw some of benchmark from Jarred Sumner twitter. it's really sad
I think you just saw a chart where Deno is slower but not the other chart
Also in Deno 1.43 there is a performance increase, but I haven't see anyone except Deno engineer who bench it
Where the hell is everyone why is the comments so empty
Owhno now we also have Bun..
Bun is more interested in speed than correctness. We'll see how that goes in the long run. I think both deno and bun will start eating into node's lunch, and both can exist together for different use-cases.
@@spartanatreyuit's hard to get enterprises onboarded with the new tools in town.
4 months later and I'm posting the third comment??