Node vs Deno. Which is Better for you? |
Posted: October 26, 2021 |
WHAT IS NodeJs? NodeJs has been a fundamental technology in recent years and its contribution to JavaScript is incalculable. However, his reign may be coming to an end. Deno is a new runtime based on Chrome's V8, developed in Rust and based on TypeScript that comes to compete directly with NodeJs. A decade has passed since back in 2009 Ryan Dahl launched NodeJs, probably one of the most revolutionary technologies of the decade because of the "madness" that it meant: JavaScript on the server. NodeJs not only diginified a language reviled by those years and also did so by offering performance that is no longer equal, if not even superior to languages ??such as Pyton, Ruby or Java. Forgive me the Javeros but in the case of Java it was not that difficult either;) NodeJs brought with it a change in mindset and paradigm. The event driven and asynchrony were not invented by NodeJS, but it is undeniable that Node has been a abandarado of asynchronous programming so widespread today. The contribution of NodeJs to the language itself was enormous and necessary. Today, a decade later, we are going to talk about Deno, also created by Ryan Dahl . WHAT IS DENO? Deno, like NodeJs, is a cross-platform runtime based on Chrome's V8 engine , with the difference that Deno uses Typescript as the default language. Although Deno follows the same architecture as NodeJs, that is, event driven, asynchronous, etc, it is a totally new project. NodeJs was written in C ++, but Deno is written in Rust and makes use of libraries like Tokio , used for Deno's Event Loop . This already gives us some clues that we can expect from Deno due to Rust's own characteristics, which is an ultra-secure language with exceptional performance. You can find more information about node vs deno in this blog and in some of mytalks . WHY DENO? NodeJs has reached maturity and like any technology it has very good, good and improvable things, which above all are accentuated with the passage of time, of which it is worth highlighting: DIFFICULTY ADAPTING TO LANGUAGE CHANGES NodeJs popularized the famous callback hell and let's say that due to its own architecture it makes it difficult to adapt to some language changes. The modules ECMAScript or promises are a good example because their support has been rather tortuous and in fact today many libraries are still using callbacks.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
|