Deno: Why you should deploy your project using Deno?
Tags: webdev, deno, node, javascript
Published: 2020-05-22 01:55:47

It was May 13th, 2020 when I saw a post about releasing of "Deno" v1.0. I was eager to know what it is. Hopefully you are too.
Deno is not a new tech buzz that is spreading nowadays everywhere in the entire spin of network. Deno is just another Asynchronous Server-side runtime environment for the popular Programming Language JavaScript. **Which was already announced by **Ryan Dahl**(The creator of Node.js) in JSCONF EU 2018** 2 Years ago.

   
   But wait... I heard many of you having so many questions coming in to your mind,

1. Why Deno?
2. When there is another Server-side ecosystem e.g Node.js then why we need Deno?
3. What are pros and cons of Deno?
4. Would it be replacing Node.js in Future?


# **History** 
 
In JSCONF EU 2018, **Ryan Dahl** talked about Deno. He stated that what are the consequences with Node.js that would improve Deno to replace it.


**_JSCONF EU 2018_**

{% youtube M3BM9TB-8yA %}

## **Why Deno** ?

**1**. Deno has great built-in security that create a difference from Node.js.It's Runtime doesn't allow the User File System, Network, execution of other script and the environment Variable.

{%codesandbox 5qhtk %}

**2**.No npm and all! Import Your favourite Package that is centralized on the third-party Package Manager and access it directly by its `URL` using `import` Keyword.
This is the biggest difference that make Deno different from the Node.js

`import { assertEquals } from "https://deno.land/std/testing/asserts.ts";`

**Note:** But what if the Website or URL from where you are accessing your module or Package is Down?
Thanks to Deno. It provides `--importmap`` feature from where you can first map the Module to your JSON and then load from the **Cache Server**. Viola! :D


**3**.Typescript Support. Yes you heard right. The Deno Core Libraries are written in RUST.The main objective of the Deno is to provide the compatibility of both *JavaScript + Typescript*. But if you love Typescript and want to use `awaits` in your project. Then Deno is here.

##**By Default Features: Out of the Box**

**1.** It is based on modern features of the JavaScript language
**2.** It has an extensive standard library
**3.** It has Typescript at its core, which brings a huge advantage in many different ways, including a first-class Typescript support (you don’t have to separately compile Typescript, it’s automatically done by Deno)
**4.** It embraces ES modules.
**5.** It has no package manager
**6.** It has a first-class await
**7.** It has a built-in testing facility
**8.** It aims to be browser-compatible as much as it can, for example by providing a built-in fetch and the global window object.



##**Deno is going to replace Node.js**?##

It will take some time cause of its application of using Typescript, from 2009 when Node.js came into the picture it has given a new direction and freedom in a way that developers can deploy their project on the top of Asynchronous Assemblies. Deno is new and would simply trigger the modern Web Technology to use its newest feature.
However, Both Deno and Node.js supports and built on the top of V8 Engine(V8 is the name of the JavaScript engine that powers Google Chrome. It’s the thing that takes our JavaScript and executes it while browsing with Chrome). Although it Node.js is 💖 So it will be going to drive the world for decades.