deno

The article is measuring full project build performance. That includes type-checking and compilation. Maybe the `tsc` type-checker was already fast (so we only get some speed improvements in `tsgo`), or the `tsc` compiler was not that fast (so we get a lot of speed improvements in `tsgo`)? *Update:* There was a performance regression in incremental type-checking between `tsgo` preview 20251209 and 20251211 [1]. But `deno` is using `tsgo` 0.1.11 which was already released last week (before this regression). So, does not seem to influence the type-checking times here. [1] https://github.com/microsoft/typescript-go/issues/2341 [2] https://github.com/denoland/deno/blob/v2.6.0/cli/tsc/go/tsgo...

Yeah it does look like things have moved on, but there were echoes from previous Go conversations around the idea of a standardised package and the attendant years of hurt that it turned me off a little while ago. I did try: https://github.com/denoland/deno/issues/4574#issuecomment-62...

At this stage I don't think either is better over the other. Deno has inexplicable high memory usage issues in Linux containers. Bun more or less suffers from the same with an added dose of segfaults. 1. https://github.com/denoland/deno/issues?q=is%3Aissue%20state... 2. https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3... Node.js is a no-brainer for anyone shipping a TS/JS backend. I'd rather deal with poor DX and slightly worse performance than risk fighting runtime related issues on deployment. Linux needs to be a first class citizen for any runtime/langauge toolchain.

You're assuming that URLPattern is performant... That doesn't seem to be the case currently. https://adventures.nodeland.dev/archive/you-should-not-use-u... https://github.com/denoland/deno/issues/19861

bun has 10x the issues matching "segfault" as deno - deno 44: https://github.com/denoland/deno/issues?q=is%3Aissue%20state... - bun 464: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...

> Note that installing Deno is probably not necessary if you don't want to, only downloading it. Just like yt-dlp, Deno is available as a fully self-contained single executable from their GitHub releases: https://github.com/denoland/deno/releases. > Yeah, you can just extract the zip and put deno.exe in the same folder as yt-dlp I hope they just make this automatic if this truly becomes necessary. yt-dlp not having requirements, or having them built-in, isn't something just "convenient", I think there's users that wouldn't use the tool without that simplicity. Most people really don't like and try to avoid having to fight dependencies.

Which is written in C/C++. Showing that Zig is not moving the needle on UB when a project becomes sufficiently complex. Take a look at Deno and check the percentage coming from FFI with unsafe languages. https://github.com/denoland/deno/issues?q=Segfault

The web api extensions and Nodejs compatibility stuff are now in deno_runtime: https://github.com/denoland/deno/blob/main/runtime/Cargo.tom... The CLI only depends on them transitively via deno_runtime: https://github.com/denoland/deno/blob/main/cli/Cargo.toml For instance I was able to run the following script using just deno_runtime with https://github.com/lrowe/deno_varnish/blob/main/src/main.rs import { DatabaseSync } from "node:sqlite"; console.log(new DatabaseSync(":memory:").prepare("SELECT 1").get());

The deno_runtime crate is indeed easy to use however the exts that provide compat for web apis and Nodejs compat still require forking deno_cli. You can use some of their ext crates https://github.com/denoland/deno/tree/main/ext but not everything. Also using ops within Workers is challenging, particularly if they share state.

For my own curiousity on a React app on my work desktop. - Clean `bun install`, 48s - converted package-lock.json - With bun.lock, no node_modules, 19s - Clean with `deno install --allow-scripts`, 1m20s - with deno.lock, no node_modules, 20s - Clean `npm i`, 26s - `npm ci` (package-lock.json), no node_modules, 1m,2s (wild) So, looks like if Deno added a package-lock.json conversion similar to bun the installs would be very similar all around. I have no control over the security software used on this machine, was just convenience as I was in front of it. Hopefully someone can put eyes on this issue: https://github.com/denoland/deno/issues/25815

I really want to like Bun and Deno. I've tried using both several times and so far I've never made it more than a few thousand lines of code before hitting a deal breaker. Last big issue I had with Bun was streams closing early: https://github.com/oven-sh/bun/issues/16037 Last big issue I had with Deno was a memory leak: https://github.com/denoland/deno/issues/24674 At this point I feel like the Node ecosystem will probably adopt the good parts of Bun/Deno before Bun/Deno really take off.

Huh, turns out it's a real bug in node resolution: https://github.com/denoland/deno/issues/30444

I have only one issue I've encountered with Deno that mattered (so to speak) and it's probably my fault. I actually created an issue for it (https://github.com/denoland/deno/issues/30433). My project config is weird (slightly more sophisticated that my repro), so, it's probably on me. Otherwise I absolutely love Deno. It makes TypeScript simple and joyful. It's the simplicity this language/tooling ecosystems badly needs in my opinion. Sometimes I feel like it makes TypeScript feel a bit more like working with Go; you can just throw a main.ts in there and build an excellent CLI from it in minutes.

Jsdom should work in deno, can you open a github issue (https://github.com/denoland/deno/issues) with some details and a reproduction? All of the simple cases I've tried seem to work fine, e.g: import { JSDOM } from "npm:jsdom"; const dom = new JSDOM( `<!DOCTYPE html><p>Hello world <img src="https://example.com/logo.svg" /></p>`, ); console.log(dom.window.document?.querySelector("p")?.textContent); // "Hello world" console.log(dom.window.document?.querySelector("img")?.getAttribute("src")); // "https://example.com/logo.svg"

I really wish they would allow you to connect to "unsafe" TLS endpoints. https://github.com/denoland/deno/issues/6427#issuecomment-65...