4 ms·
Every Node.js dev should be thanking the Deno creators. It has forced them off of their "this is how Node does it" complacency. Most improvements I notice and c
by pseudosavant 5y ago
Every Node.js dev should be thanking the Deno creators. It has forced them off of their "this is how Node does it" complacency. Most improvements I notice and care about on Node these days are all things that Deno already supports (fetch, ES modules, async std lib uses promises, etc).
The Web Platform APIs aren't perfect, but they are better, and more thoroughly thought out than Node's.
- inglor 5y agoWhat is "this is how Node does it" complacency you speak of? Node has been talking about Fetch since at least 2018 _before_ Ryan even announced Deno. This is true for promises, ESModules etc. Ryan _attended those meetings_ in the Node collaborator summit. Don't get me wrong I am thankful for Deno (and a contributor!) but: - It's a lot easier to make changes when the project is new and you don't have a lot of users (which is great for Deno) whereas Node has a whole (huge) ecosystem to consider on every change. - It's a lot easier to make changes with venture capital and funding to hire a bunch of people to work on it full time vs. a project with a "regular" MIT license where the code is owned by the community and not a company. Those are not complaints about Deno, I like Deno (and not just Ryan, Lucas, Kit, Ben and the other people are nice and helpful and the project is really nice). It's just to explain very little of Node's innovation is (at the moment) driven by Deno.
- inglor 5y ago@dang I can't seem to be able to edit this is there any way to fix the formatting by any chance?