We need to give credit Ryan Dahl for making node.js, regardless of whether you don’t care for it – and there are a lot of individuals who don’t. Presently he is thinking that he might have done better.
The issue with node.js is in the tinier things that at first didn’t appear to be so vital, however after some time they have and are present shows its importance. Giving his statements at JSConf EU, Ryan Dahl concedes that he committed errors – for the most part with security and how modules are overseen. He includes that there are such a large number of clients that rely upon it and there is no real way to transform it.
Subsequent to investing energy far from node.js, working with Go, Dahl just presently came back to the node and wasn’t upbeat about what he encountered. He is as yet excited about its fundamental engineering – the nonconcurrent approach that abstains from threading.
The way it is by keeping away from the module framework, it doesn’t utilize npm – he doesn’t care about assembling a framework for them, module names, and folders.
Deno attempts to do things right this time and who preferred to hit the nail on the head over somebody who has failed to understand the situation and let it be known. Deno is as yet exploratory.
The undertaking is on GitHub and keeping in mind that in its early days it has 27 benefactors which are useful for a startup venture.
So will node.js offer an approach to Deno?
I question it.
And the bottom line is even though the creator of Node.Js believed that his invention is not that amazing we truly know how helpful it was for this reason we are very thankful that we have the privilege to have such environment.