Just a little info, in case you didn`t know:
the developer of node, dropped node and replaced it with Deno, because node was to much of a mesh to maintain because of all the dependicies.
So thats got me thinking, why is so much work put into node.js, if its dead and dropped…even by the man who wrote it.
I dont quite get it…
NodeJS is not dead and it probably will never die. NodeJS is just as relevant in 2022 even though the hype has stabilised.
Actually, Ryan Dahl still uses it today. The reason why he chose to develop Deno is because he sees that NodeJS can be improved on. These improvements, such as using Rust instead of C/C++, have no effect on us developers and we should not be jumping ship because of a perceived passing away of NodeJS.
There are some key things to consider about Deno that attempt to solve problems with NPM
- Secure defaults : Explicit permission must be granted for your Deno applications in order to access disk, network, and runtime environments.
- Native TypeScript support: No tsconfig needed—Deno acts like a native TypeScript runtime. Under the hood Deno still transpiles and bundles TypeScript files.
- Ability to import ES Modules directly from URLs : No more NPM—dependencies can be imported directly via URL or file path:
Deno also includes less-cited features that I’m excited about:
- Bundler : Deno can bundle your application and its dependencies into a single file.
- Script Installer : Deno can install a script from any URL, add its command-line alias to PATH, and requires explicit permissions during installation. Wow!
- Async Standard Library : Deno standard APIs use async/await and async iterators.
- Built-in test framework : Deno includes a built-in test framework with top-level async support.
Robert Zhu is a Principal Developer Advocate at Amazon Web Services. He focuses on APIs, Web, Mobile, and Gaming. Prior to joining AWS, he worked on GraphQL at Facebook. While at Microsoft, he worked on the .net Framework, Windows Server, and Microsoft Game Studios.
and
This repository is a fork of Deno Land’s Deno repository, created so that Bloomberg’s engineering team can collaborate with each other (and the rest of the Deno community) on enhancements to Deno. Branches in this repository represent ‘work in progress’ that will be contributed to the Deno Land Deno repository when the work is ready for review.
Deno looks interesting and is already in use
Ryan Dahl, creator of Node.js,
Why use Deno?
Deno’s features are designed to improve upon the capabilities of Node.js. Let’s take a closer look at some of the main features that make Deno a compelling alternative to Node.
Security (permissions) in Deno
Among the most important of Deno’s features is its focus on security.
As opposed to Node.js, Deno by default executes the code in a sandbox, which means that runtime has no access to:
The file system
The network
Execution of other scripts
The environment variables
It’s all about ecosystem, community and potential. It’s not about who created it in the first place. NodeJS is safe for now. Not saying it’s going to be here forever. In 5 years time we can reevaluate the situation.
I can remember when NetBeans was going to be the magic Work-on-all-platforms solution.
The point of Coffee Lounge is to allow free communication because the future in Tech is the future that is talked about NOW.
That node.js is the latest greatest it becomes all the more interesting and informative to know that the same genius has created an upgrade, so to speak, of his own invention.