TL;DR
Deno was created by Ryan Dahl, the creator of Node.js.
Deno is secure by default. Without permission, it cannot access files, net...
For further actions, you may consider blocking this person and/or reporting abuse
The problem with callback hell in Node has been solved a long time ago. Most features of modern js has been or are being incorporated in node. For example, It is possible to use top-level await with Node (with some set up) even though it is still ECMAScript proposal.
I see extensive use of callbacks only in training videos as an example of how not to do it. What version of Node are using?
Thanks for your comment.
Yes, Node.js has updated a lot recently and with some configuration can bring in more modern JavaScript syntax. I just appreciate that Deno has all of this by default. Whereas, as you mentioned, features like top-level await in Node.js require some set up.
Also, some people still use the callback style. It will take a while for everyone to catch up and for people to take on new programming styles. Deno just provides a way to skip that process and work with a more modern API without legacy issues.
Either way, I'm excited for the Deno project :)
I don't think "don't need to NPM install all your packages" is solving anything, or am I misunderstanding something? You don't get the benefit from a management mechanism AND have to reference dependencies over and over again in your files?
Great question.
It does follow the standard of using URLs for pulling in packages that GoLang employs and what the Web is built upon. The versioning can be solved by deps.ts file which Deno is currently using also. Deno is following in the footsteps of other projects and learning from them to create a (hopefully) better third-party package system.
I understand the concern that you might have, it's understandable. The good news is that the Deno project is very deliberately going in this direction. So a lot of thought has gone into it.
I highly recommend watching Ryan Dahl's talk announcing Deno. He talks about his reasons and you learn a lot about Node.js along the way. Definitely worth a watch. You can see it here
I'm still curious (and doubtful):
This discussion mostly covers all my concerns: github.com/denoland/deno/issues/47
I've started using deno for my one off scripts, was very pleasant. Love top level async/await.
I just use TypeScript with ts-node where I can find more libraries.
Most Node libraries work with Deno. Check PIKA.DEV and JSPM.IO, or follow the tutorials on how to make conversion of packages.
Technically, any package that is valid JavaScript (and not NodeJS JavaScript) is a valid Deno module.
Jspm.io sounds interesting,
How do you publish a package with deno?
There's a package repository deno land, but you could just push to a git repo on GitHub or GitLab
Seems we can also use the pika PKG CDN around npm packages👍
Thanks Sean! 🙌
Yes but can we get the package with semver?
Seems interesting, I love the Typescript support out of the box, thanks for the article!
Glad you liked it!
Next JS Runtime
Done
Node.js and Deno.js are run times for JavaScript. So if you can write JavaScript you'll be ready to go!
Didn't know about the project. Very interesting! Thank you. I'm gonna give deno a try. BTW how is it pronounced? Deeno? 🤔
Haha yeah, there has been some confusion about the pronunciation. It started as Deno (short 'e') and now is Deeno (long 'e'). It has a lot to do with the logo of the Dinosaur. You can watch Ryan Dahl (the creator) talk about it here. I've time stamped it so you can skip straight to where he starts mentioning it.
I heard about Deno some time ago. I think is time to investigate a bit more. Thanks for the article, the collection of resources you posted is perfect to start learning about.
You're welcome! Enjoy your journey in Deno!