For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Luxand.cloud -
Akpevwe11 -
temaweb10 -
Jima Victor -
Latest comments (9)
Too late. The size of NPM prevents an intruder. Now Microsoft owns it and they excel at creating compilers. Dependency issues will most likely vastly improve in short order.
Define replace?
Will Deno be maybe the first choice if you start a new project in a few years? Maybe. Maybe only for startups or maybe only for big companies with the time and manpower to developer all the tooling.
Will NodeJS code be used in production and maintained in 10 years? I bet on it. Mainframes from the 80s are still a thing.
Will we maybe see something else then deno and nodejs in 5 to 10 years? Sure, maybe we will use only wasm and write everything in future-language-which-we-don-t-know-yet
I think Deno will become more popular and we will start seeing big things being created with it. We may even see a few things migrate to it. But, Node.js has such a large usage and ecosystem I don't see how we can get rid of it. It would be like getting rid of Wordpress or PHP. Those things are still here after many, many years of Node.js being available. I do look forward to learning more about it in the next few weeks and maybe even creating an application with it.
It's really hard to usurp things with the network effects that NodeJS has, I don't think the Pros on the Deno side are compelling enough for replacing NodeJS in an application right now but we'll certainly see it used in greenfield projects.
Definitely looking forward to following the progress and using the lambda standard library.
Anything is possible in the programming community. It would be easier to answer if your question had a period included in it, as to whether you're asking about the current period or the future. 🙂
As of current scenario, Deno is young. There are a lot of pros of using Demo in a project when compared to Node.js . Keeping this aside, it is not as easy as we imagine to change huge applications from Node.js to Deno or any other library for that matter.
So it will take time for the community to start understanding, using, and replacing Node with Deno. And also Deno might not be in a position to provide all the features that Node provides us with.
Deno courses and crash courses will be out, people will learn them and get used to it. Start-ups will start using it in their products. And then we will see a rise of Deno in the production slowly, hopefully.
So end note is: Node.js is going nowhere, it is as strong as how it was last week
Thanks🙂
Tharun Shiv
I say no. They only way to do that is by being 100% compatible, and as far as I know that's not a goal for Deno.
Another thing, the size of node's ecosystem is too big to be replaced. The internet told me years ago that node was going to "kill" PHP and yet here we are. PHP is still out there.
I agree, the size of the ecosystem is far too large to suddenly change now. It took forever for even basic hosting platforms to support NodeJS. I expect it will be a while before Deno really gets adopted as well.
Who knows :D
You can read a few opinions about it:
Explain Deno Like I'm Five
Ben Halpern ・ May 11 ・ 1 min read
Thanks for sharing. Will do. Stumbled on Deno today. Everyone is talking about it.