KKkkirsche·Dec 22, 2020
For anyone else curious, I believe Deno is a reference to https://github.com/denoland/deno please correct me though if that’s wrong
In Dyon – A Rusty dynamically typed scripting languagedenoland
deno
Rust2018–2026
denoland / deno
deno
A modern runtime for JavaScript and TypeScript.
161Distinct people
202Mentions
1Explicit recommenders
108.9KGitHub stars
What to know before exploring
What it is
A modern runtime for JavaScript and TypeScript.
GitHub
Where it is used
What people are saying
I love Deno and I use this, but I really wish they would fix this dumb bug: https://github.com/denoland/deno/issues/16466
IshKebab used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- oven-sh/bun · linked in 6 of the same discussions
- libuv/libuv · linked in 3 of the same discussions
- denoland/rusty_v8 · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year202 dated mentions
Observed mentions: 2018-08-23 15:35:35 UTC to 2026-10-16 06:53:01 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 16 | 4 | 12 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 45 | 18 | 27 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 30 | 4 | 26 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 33 | 4 | 29 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 30 | 1 | 29 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 18 | 0 | 18 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 13 | 1 | 12 |
What Hacker News says
45 sourcesDeno 1.6 lets you compile TypeScript to a single executable
2 points · Open discussionNot yet[1] likely to see WebCrypto first and/or something similar to Node's crypto library. You could probably get away with wasm build of a C/C++ or Rust library if you don't mind getting dirty.
1. https://github.com/denoland/deno/issues/1891
edit:
partial webcrypto/wasm option already available
https://deno.land/x/god_crypto@v1.4.1
In Deno 1.6 supports compiling TypeScript to a single executableDeno 1.6 supports compiling TypeScript to a single executable
657 points · Open discussionI think deno pkg.json permissions are process-level not library-level
I'm concluding that only by this very old thread; I'm not up-to-date with deno + could be wrong
https://github.com/denoland/deno/issues/171
In Malicious NPM package opens backdoors on programmers' computersNote that Deno is missing locale support. So for example this:
(1000).toLocaleString();
will get you "1,000" with Node, but "1000" with Deno:
https://github.com/denoland/deno/issues/1968
In Deno 1.4The ticket for TLS support was closed in December (https://github.com/denoland/deno/issues/1568) and there seems to be a lot of TLS support including esoteric use cases now.
In Deno 1.4> I've never seen someone who wants to go back from TypeScript to plain JavaScript.
This is a very specific case, but it can happen: https://github.com/denoland/deno/pull/6793
In TypeScript 4.0Due respect, these are issues with how the Deno team uses Typescript, not with the language itself.
> TypeScript compile time when changing files takes several minutes, making continuous compiling an excruciatingly slow process
Umm, you can compile single files, and serve them individually. It's no different from bundling (e.g. with webpack) Javascript.
> The Typescript structure that they’re using in the source files that create the actual Deno executable and the user-facing APIs is creating runtime performance problems
Then use a better structure?
? TypeScript isn’t proving itself helpful to organize Deno code. On the contrary, the Deno team is experiencing the opposite effect. One of the issues mentioned is that they ended up with duplicate independent Body classes in two locations https://github.com/denoland/deno/issues/4748
Then cons
Read the rest
olidate the two classes...? How is the the language's fault?
> The internal code and runtime TypeScript declarations must be manually kept in sync since the TypeScript Compiler isn’t helpful to generate the d.ts files
Well, it can be. Fix your build rules.
> They’re maintaining two TS compiler hosts: one for the internal Deno code and another other for external user code even though both have a similar goal
Again, not the language's fault.
---
We've been using Typescript for a couple of years now, and it's been great. By trying to do things the right way, it actually forces us to organize our code better. I think the Deno project would benefit from refactoring their code to solve their issues, instead of blaming the tools.
They are considering switching from tsc to a TypeScript compiler written in Rust[0][1], and `deno fmt` subcommand already uses it internally.
[0] https://github.com/denoland/deno/issues/5432
[1] https://github.com/swc-project/swc
In Design Doc: Use JavaScript instead of TypeScript for internal Deno CodeDeno uses the web standard Worker API to implement sub processes. They are also working on fine-grained permissions for these workers [1].
[1] https://github.com/denoland/deno/issues/4867
In What the Hell Is a Deno?Packaging to standalone executable is being worked on
https://github.com/denoland/deno/issues/986
In What the Hell Is a Deno?https://github.com/denoland/deno/blob/9090023c33de7b64ae4142...
Deno runs js in v8 and all syscalls go through the rust runtime. The limitations are pretty coarse (but i'd say a great start).
In Deno Is a Browser for CodeAccording to its architecture description ¹, there are no containers or virtualization involved in Deno.
I found deno::CoreIsolate in the source ². Userland process isolation seem to be provided by V8 Isolate.
The execution and security model remind me of recent trend in FaaS, in particular running WebWorkers (or similar), WASM, etc. Found a fascinating presentation about how V8 is used at CloudFlare ³.
"..using V8 isolates instead of containers or VMs, achieving 10x-100x faster cold starts and lower memory footprints.."
---
¹ https://deno.land/manual/contributing/architecture#schematic...
² https://github.com/denoland/deno/blob/2610ceac20bc644c0b58bd...
³ Fine-Grained Sandboxing with V8 Isolates - https://www.infoq.com/presentations/cloudflare-v8/
In Deno Is a Browser for CodeShowing the 15 most recent of 45 sources. Enable JavaScript to search and browse every indexed mention.