DEV Community

Discussion on: Here's Actually Why Deno Flopped

Collapse
 
jerilseb profile image
Jeril Sebastian • Edited

Deno 1.0 has been out for only 5 months and you call it a flop. By that measure, languages like Python and Rust were flops too.

Regarding the absence of a central package management repository like NPM, Deno has taken that inspiration from Go, and Go is hardly unsuccessful. If you really want to, you can use easily NPM packages in Deno using tools like jspm.org/. The fact is NPM comes with a plethora of security issues, which Deno wanted to avoid. Deno will eventually support import maps (deno.land/manual/linking_to_extern...) which can act as your package.json if you like.

Also, one of the main goals of Deno, which you missed, is native Web APIs compatibility. Means, most of your Browser knowledge will just carry over to Deno, and vice-versa. So you don't have to juggle between two different sets of APIs. All non-web-standard APIs are namespaced under the Deno namespace. That means, remove all Deno namespace references and your code will run in a Browser. To me, that alone is a game-changer for Deno.