DEV Community

Discussion on: Explain Deno Like I'm Five

Collapse
jsn1nj4 profile image
JSn1nj4‍‍👨‍💻 • Edited on

I wondered about that last point myself. No doubt there will be projects that can take advantage of Deno, but the Node ecosystem and market share are huge. It would take a long time for this kind of transition to happen.

Collapse
rehmatfalcon profile image
Kushal Niroula

Among other things, Deno is a great replacement for utility scripts that may have been historically written with bash or python.

The above is from the introduction page of Deno. So, maybe Node and Deno won't compete but co-exist. Deno seems, at the moment, focused to make CLI apps generation easier, or at least that is what I gather from the above quote.

Thread Thread
jsn1nj4 profile image
JSn1nj4‍‍👨‍💻

That sounds interesting.

Also, I realize you have to explicitly give Deno certain permissions at runtime, but I'm skeptical of the idea of using ES module imports with third-party URLs for server-side code. Maybe I just need to read up on that...

Thread Thread
rehmatfalcon profile image
Kushal Niroula

Yes, I think that will be addressed in some way as the platform matures. However, researching before using a third party package/URL is a must. So, we need to ensure that we only use those packages that we absolutely trust.

The other issues have been solved by the Deno team already. Mainly, importing the packages and exporting them; this ensures that we know the packages that we are using and that we use only single version of any library/package. Next, the Deno automatically caches code the first time we install dependencies, so our software won't break because of change in code from the URL. We could also version control our dependency if we want.