Brought to you by engine.so - a tool to instantly create a public self-service knowledge base for your customers with Notion.
Deno is a Javascri...
For further actions, you may consider blocking this person and/or reporting abuse
Dude, Deno exists for two years. It has a long way to go before being remotely mainstream. Don't judge it too soon. Do you remember where Node has been in 2011? Or React in 2015?
If you thought releasing v1 would make it explode - you are wrong. It's a small step in the right direction. Having played with it for a very small personal project, it is still far from production ready. But as more people rally around this technology, it will become more and more viable in large scale.
Dropping NPM was a design decision, and only the future will tell if it was the right decision. NPM suffers from a lot of issues in itself, and Deno takes an interesting new approach to solve those issues.
Lastly, even if Deno will never take off (although I personally hope it does), it shows us that there is another way, and that's always a good thing.
Ryan living in 2030+
If you take a look at their repo there's currently 608 issues and 60 open PRs. Lots of work to be done. It looks like they're focusing on that rather than the UX. If you look throughout the various repos under
denolandyou will see there are many roadmaps still in their early stages. Once these are addressed to a more reasonable degree I'm sure teams and companies will take a risk on deno, with or without NPM compatibility.I'd like to see deno become robust and intuitive enough to outlive node by a longshot.
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.
I think it's quite early to call a flop, as we can read from interviews with Ryan Dahl, Deno's creation is has many things to do with Ryan experimenting with Machine learning(Deno as not just another web server runtime). With native WebGL(or WebGPU in near future) available Deno will act something like go to scripting language for ML, Data science. I personally hope Deno/JS will have huge role in Data science, ML related future. Moving from largely python operated world of DS.
Same adoption challenges faced by every new product. A big boost to Deno would be a wide usage by one of the big corps.
I'm not quite following Deno development but what are some examples of codebases purely built on it?
I've a small event handler build with deno, mostly for calling telegram api, email, and some other services. I really like that with deno 1.5 or so you can actually bundle your app into a small bundle.js file, mine is about 600kb of pure js with all deps included, and you can read it very easily.
I don't agree with you, I'm a NodeJs developer and really want to use deno as fast as their ecosystem is being reliable, from the perspective of built in module stability, frameworks, community libraries, etc.
One of the advantages using deno is their module system, You've wrong place when you think this is a replacement for NodeJs, it's like super version of NodeJs, because like the module System without npm is a big win for me, nowadays NodeJs developers are struggling with the big amount of npm module (that's why pnpm so popular), also the security and bloated dependencies are the big issues.
So being able to have a smaller app within the container (like a docker) is a ++. Because npm_modules is not going to be anywhere without this breakthrough, also it is fun to have a small containerized app (with Deno) to scale fast and massively on the production server.
Have you ever heard about Deno is able to compiled as a Binary app? But, still needs an V8 runtime absolutely, and maybe one day that could be a possibility to run like a static binary (like Go)
Just adding to the discussion, without being any expert or even having ever developed anything in either Node or Deno.
Deno 1.0 was released in May 2020. In the middle of a health+economic crisis which virtually stopped economies all over the world. I don't know the effects of this in the developers community but I wouldn't analyze any indicator without taking this onto account.
First of all, in the Javascript world, the hype cycles are massive and unstoppable. By default, Deno should take off as a "better Node", especially since this is effectively Node 2 - from the same author.
Secondly, claiming that it does not have enough features to switch to does not check out. Businesses routinely choose to spend hundreds of hours and millions of dollars implementing and maintaining, say, Kubernetes, which the vast majority of companies has no business doing, as they simply don't have the type and scale of problems it was designed to solve.
Deno was being like rust. Gaining stability and sitting in the background. It never flopped.
And like you predicted, npm support is here in 2023.
The title here could change a little.
title is total clickbait and should be changed to stop the SEO