<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh" -->

---
title: Why We Chose Node.js Over Deno? | daily.dev
description: Node.js was the de-facto standard for writing server-side JavaScript apps in the 2010s. Ryan Dahl introduced Deno in 2018 in his controversial JSConf EU talk...
canonical: https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Why We Chose Node.js Over Deno? | daily.dev
og:description: Node.js was the de-facto standard for writing server-side JavaScript apps in the 2010s. Ryan Dahl introduced Deno in 2018 in his controversial JSConf EU talk...
og:url: https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh
og:image: https://api.daily.dev/og/posts/O3YUQVAVh.png
og:image:alt: Why We Chose Node.js Over Deno?
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why We Chose Node.js Over Deno?

**[Amplication](https://daily.dev/sources/amplication)** · 7 min read · 136 upvotes · 21 comments

## Summary

Node.js was the de-facto standard for writing server-side JavaScript apps in the 2010s. Ryan Dahl introduced Deno in 2018 in his controversial JSConf EU talk titled "10 Things I Regret About Node.JS" This article gives an overview of the platforms, history, performance, security, and all other critical features.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://amplication.com/blog/why-we-chose-nodejs-over-deno>

## Community discussion

Top comments from developers on daily.dev.

**@thomashighbaugh** · 10 upvotes

> **Question**: `Why Chose X or Y?`
>
> **Answer Every Time**: It depends on the context

**@raythurnevoid** · 7 upvotes

> "Node.js uses the commonJS module system, while Deno uses the ECMAScript module system." This is false, node is compliant with the latest ecmascript specs, additionally node supports commonjs for Legacy code.

**@yuvalhazaz** · 6 upvotes

> Hey there, daily.dev community! Just dropping by to say thanks for sharing our post. @mulyg put a lot of thought into writing this, and we're thrilled to see it resonate with you all.
>
> We believe that the choice between different technologies is never black or white. In our case, while we respect the innovations Deno brings to the table, we found Node.js to be a better fit for our specific needs at this time. We hope that sharing our thought processes and the factors we considered will help others in their own decision-making.

**@ahmdrzalifa** · 4 upvotes

> node is industry standard, can find people easily with good skills.

**@kyoukhana** · 2 upvotes

> Lets throw in Bun as well.  Bun is much faster then Node

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments
- [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments
- [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#javascript](https://daily.dev/tags/javascript), [#tools](https://daily.dev/tags/tools), [#community](https://daily.dev/tags/community), [#nodejs](https://daily.dev/tags/nodejs), [#backend](https://daily.dev/tags/backend), [#typescript](https://daily.dev/tags/typescript), [#npm](https://daily.dev/tags/npm), [#deno](https://daily.dev/tags/deno)

[View this post on daily.dev](https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Why We Chose Node.js Over Deno?","url":"https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh"},"datePublished":"2023-06-09T06:08:34.981Z","dateModified":"2023-07-20T14:10:56.027Z","description":"Node.js was the de-facto standard for writing server-side JavaScript apps in the 2010s. Ryan Dahl introduced Deno in 2018 in his controversial JSConf EU talk...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/92d2cdcc21d485876e7671b772eaa064?_a=AQADKdt","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/92d2cdcc21d485876e7671b772eaa064?_a=AQADKdt","isAccessibleForFree":true,"articleSection":"Amplication","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Amplication","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/81a4f43fc0b84e55b9f61cbae4ec745a","url":"https://daily.dev/sources/amplication"},"commentCount":21,"discussionUrl":"https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":136},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":21}],"keywords":"security,javascript,tools,community,nodejs,backend,typescript,npm,deno","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Amplication","item":"https://daily.dev/sources/amplication"},{"@type":"ListItem","position":3,"name":"Why We Chose Node.js Over Deno?"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-we-chose-node-js-over-deno--o3yuqvavh","comment":[{"@type":"Comment","text":"Question: Why Chose X or Y?\nAnswer Every Time: It depends on the context","datePublished":"2023-06-09T10:25:52.455Z","url":"https://daily.dev/posts/O3YUQVAVh#c-1wklJkiCo","author":{"@type":"Person","name":"Thomas Leon Highbaugh","url":"https://daily.dev/thomashighbaugh","image":"https://avatars.githubusercontent.com/u/32242061?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10}},{"@type":"Comment","text":"“Node.js uses the commonJS module system, while Deno uses the ECMAScript module system.” This is false, node is compliant with the latest ecmascript specs, additionally node supports commonjs for Legacy code.","datePublished":"2023-06-09T12:45:08.304Z","url":"https://daily.dev/posts/O3YUQVAVh#c-fTnOraVt8","author":{"@type":"Person","name":"Ray Thurne","url":"https://daily.dev/raythurnevoid","image":"https://lh6.googleusercontent.com/-HEk4FtpXDwY/AAAAAAAAAAI/AAAAAAAAAAA/AMZuuckP08Z9z3CuZelxMlZtWfMMqQzYNw/s100/photo.jpg"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7}},{"@type":"Comment","text":"Hey there, daily.dev community! Just dropping by to say thanks for sharing our post. @mulyg put a lot of thought into writing this, and we’re thrilled to see it resonate with you all.\nWe believe that the choice between different technologies is never black or white. In our case, while we respect the innovations Deno brings to the table, we found Node.js to be a better fit for our specific needs at this time. We hope that sharing our thought processes and the factors we considered will help others in their own decision-making.","datePublished":"2023-06-09T06:22:40.287Z","url":"https://daily.dev/posts/O3YUQVAVh#c-qEGsg72tF","author":{"@type":"Person","name":"Yuval Hazaz","url":"https://daily.dev/yuvalhazaz","image":"https://avatars.githubusercontent.com/u/43705455?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6}},{"@type":"Comment","text":"node is industry standard, can find people easily with good skills.","datePublished":"2023-06-09T11:54:32.554Z","url":"https://daily.dev/posts/O3YUQVAVh#c-xDSy2XP9u","author":{"@type":"Person","name":"Ahmad Raza","url":"https://daily.dev/ahmdrzalifa","image":"https://lh3.googleusercontent.com/a-/AOh14GgglD4dTEiqB7uLMez-1WrR-KzAAHVAzyL1o6Btdw=s100"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}},{"@type":"Comment","text":"Lets throw in Bun as well.  Bun is much faster then Node","datePublished":"2023-06-09T11:28:22.570Z","url":"https://daily.dev/posts/O3YUQVAVh#c-Ig7o1Dyls","author":{"@type":"Person","name":"Kevin","url":"https://daily.dev/kyoukhana","image":"https://avatars2.githubusercontent.com/u/756849?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}}]}
```

