this post was submitted on 13 Jul 2026
68 points (95.9% liked)

Programming

27697 readers
325 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BB_C@programming.dev -5 points 21 hours ago (1 children)

Bun is a TypeScript runtime, like a faster NodeJS.

I guess the target audience is non-coding AI skeptics looking for pseudo-intellectual takes, which appears to be a growing market. Because getting the very first technical detail, and a very basic one at that, this wrong is not a good look.

[–] assaultpotato@sh.itjust.works 9 points 19 hours ago (1 children)

https://bun.com/

HTML title: Bun: A fast all-in-one JavaScript runtime

Bun is designed as a drop-in replacement for Node.js

https://bun.com/docs/runtime

execute javascript/typescript files [...] with Bun's fast runtime.

Am I missing something? How is that claim incorrect? I've never used Bun but their marketing material lines up exactly with the claim.

[–] BB_C@programming.dev -2 points 19 hours ago* (last edited 19 hours ago) (1 children)

First of all. Strictly speaking, there is no such a thing as a TS runtime. TS compiles to JS.

Second of all, bun binds against JavaScriptCore, which is the JS engine used in Safari. Node binds against V8, which is the engine used by Blink (Chromium et al). Both are implemented in C++. And the latter is considered the fastest engine.

Ironically, both engines are mentioned by name in the very bun blog post being discussed, which points to a problem that is almost bigger than mere tech literacy from the pseudo-intellectual OP.

[–] assaultpotato@sh.itjust.works 6 points 19 hours ago* (last edited 19 hours ago) (1 children)

Saying there's no typescript runtime is (imo) a bit pedantic - if you JIT transpile TS down to JS at run time with hot-reloading you're effectively a TS runtime. For a non-technical one-liner on Bun, I feel that is a very reasonable simplification to make.

Perhaps bun would be even faster if they bound against another JS API, but that doesn't mean that Bun isn't faster than Node.js. They claim it's 3x faster than Node in aggregate, and that can potentially be true even if they use slower machinery under the hood. Python is a slow language but a fast framework can outperform a poorly written C++ implementation.

I'm not going to defend the article, I have no horse in that race, but until I see benchmarks that say Bun isn't faster than Node in aggregate, I don't think the claim can be called "wrong" on its face.

E: that's exactly what Bun does: "Bun supports TypeScript and JSX with no configuration. Bun transpiles every file on the fly with its native transpiler before running it."

[–] BB_C@programming.dev -2 points 14 hours ago

I'm going to call cargo a Rust runtime from now on, considering cargo-script exists.