3 ms·
Is it pretentious because he said he wrote the talk the night before? (It is Ryan Dahl giving the talk and he's pretty famous for writing Node.js originally.)
by freeqaz 4y ago
Is it pretentious because he said he wrote the talk the night before? (It is Ryan Dahl giving the talk and he's pretty famous for writing Node.js originally.)
It's interesting the goals that he outlines at 3:30. They feel like the same goals as what Bun has for the project. I'll paste them below (thank you iOS image OCR)
> My Dream Stack
> - Reduces boilerplate
> - ideally very small apps can be defined in a single file
> - Uses JavaScript, the universal scripting language
> - Async I/0 and optimal HTTP server performance
> - Built-in, uniform dev tools - code formatter, linter, doc generation, etc
None of those describe the goal of what my understanding of Dyno has previously led me to believe: Security around 3rd party dependencies. (They've forked the entire NPM ecosystem to make this possible, and this is the key differentiator between Bun and Dyno in my mind.)
- verdverm 4y agoIt's pretentious because he sounds like he knows what is better for everyone, while he "fixes" his previous mess up by fracturing the ecosystem and introducing more tooling. Beyond N browser support, we are now going to see a host of tools to support Node <-> Deno translation. So it seems he has added a dimension of complexity while claiming to reduce it. The part about unix being wrong was notably wrong itself
- fendy3002 4y agoI don't know why deno is veered off hard from package.json and node ecosystem rather than supporting it and enhancing from it. It makes adapting deno a hassle and hard than transitioning nicely from node.
- verdverm 4y agoIt's going to be a hard case to make to management, while bun is a drop in replacement, for npm, that does make a small part of JS better I wonder if Deno as a word is a premonition for what it will do to node, split in the middle and rearranged to look shinny again
- verdverm 4y agoTurns out bun is not a drop in replacement and has decided to make its equivalent of package.json a binary file... smh
- eyelidlessness 4y agoMy understanding (which I’m sympathetic but not married to) is because Deno’s module system, along with those of the web APIs it embraces, provide a sufficient abstraction layer for `npm` (the client, not the business) to be built on. Various approximations of this are good enough that people are using Node and Deno almost interchangeably. The extent to which they don’t work mostly boil down to packages expecting a fully complete Node environment or a fully complete browser environment.