Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I am worried about Bun

wwj.dev

Post reply on HN
Print view View original

261–270 of 368 posts

Re: I am worried about Bun

#261

Post by notnullorvoid »

thot_experiment wrote: post #227

Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…

I switched to Deno because it is the only option out of the 3 that allow monorepo workflow without building .d.ts files. Bun and Node both do type stripping or compiling of TS, but it only works for the entry package of the running script, not any of the linked dependencies from the same repo.

There are still things I dislike about Deno, but it really does make package development a lot simpler. JSR is a great upgrade from NPM, and Deno makes it so simple to publish to both NPM and JSR. Strict IO permission system and WebGPU support are also nice to have.

> wrap a project into an `*.exe`

Deno makes this simple too. Though that's where it's bundling features stop. Honestly I am okay with that, I'd rather use Rolldown or Vite for web or library bundling.

Re: I am worried about Bun

#262

Post by oasisaimlessly »

semiquaver wrote: post #184
AntonyGarand wrote: post #11

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

I disagree with the overall premise: Before the acquisition, GitHub had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (Embrace, Extend, Extinguish, MS Windows), it's a stretch to assume this will also translate into making GitHub worse: Being worried makes sense but I remain optimistic about GitHub.

You dropped this:

Re: I am worried about Bun

#263

Post by coalstartprob »

Jarred wrote: post #211

I work on Bun, and this post is confusing to me. Me personally and the Bun team continues to dogfood & make Bun better everyday. Our development pace has only gotten faster. Bun's stability has improved significantly since joining Anthropic. Here are some things shipping in the next version of Bun: - 17 MB smaller Windows x64 binaries [0] - 8 MB smaller Linux binaries [1] - `--no-orphans` CLI flag to recursively kill…

[dead]

Re: I am worried about Bun

#264

Post by traderj0e »

thot_experiment wrote: post #252
crubier wrote: post #243

Earlier quoted context omitted.

The Bun DX is infinitely better than Node's, especially for Typescript projects

In what particular way? I've been using Typescript a lot more recently (unfortunately XD) and I've found the native experience in Node to be totally fine.

Node's built-in profiler doesn't work with Typescript, which is one part of Node not natively supporting TS. Idk how it is in Bun, cause that made me abandon TS rather than abandoning Node.

Re: I am worried about Bun

#265

Post by traderj0e »

afavour wrote: post #254
jpsimons wrote: post #237

Earlier quoted context omitted.

Sure, but at least on Node 22 I think I have to pass `--env-file=.env` option to make it pick up .env.

Certainly true but there’s a line between “better DX” and… well, kinda laziness

Yeah I don't want it to silently read magic config files

Re: I am worried about Bun

#266

Post by traderj0e »

So who controls NodeJS? https://openjsf.org/governance has Microsoft as the chair. And Microsoft owns npm. It's kinda hard to avoid a corp controlling these tools.

The author seems more focused on the thing where Anthropic fights OpenClaw usage unless you have the right billing set up for that. Frankly I just don't care about those complaints, all the LLM services want you to set up a non-subsidized billing method to use OpenClaw because it uses lots of tokens. It doesn't mean they're going to crap on Bun.

The only reason I don't use Bun is I never ran into a situation where Node didn't cut it. Even though my least favorite tech corp controls Node.

Re: I am worried about Bun

#267

Post by pocksuppet »

munk-a wrote: post #155
sroussey wrote: post #151

Earlier quoted context omitted.

One could argue that AI has already started to hoover up all the world’s resources. AI buildout as a percent of GDP is already high and still rising.

Don't blame machines for our folly. This is just standard bubble behavior.

What if that's just the mechanism the machines take over the world?

Natural selection doesn't care why something replicated a lot.

Re: I am worried about Bun

#268

Post by stopachka »

This post seems to "throw doubt" on Bun, based on the OP's experience of Claude Code. But this seems unnecessary indirect. It's not like Bun is hidden software: it's open source and actively developed.

So the more direct question would be: How has Bun actually been since the acquisition?

From what I can tell they have been responding to users as fast as before, and improving the product as well as before.

Re: I am worried about Bun

#269

Post by SOLAR_FIELDS »

notnullorvoid wrote: post #261
thot_experiment wrote: post #227

Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…

I switched to Deno because it is the only option out of the 3 that allow monorepo workflow without building .d.ts files. Bun and Node both do type stripping or compiling of TS, but it only works for the entry package of the running script, not any of the linked dependencies from the same repo. There are still things I dislike about Deno, but it really does make package development a lot simpler. JSR is a great upgrad…

Deno has been great for wrapping the dozens of REST API's I need to use in the world in MCP. The no compilation thing means that I can push and it's literally deployed in seconds. I run several dozen of the little servers for various use cases, it's a very cheap way to build an automatable life

Re: I am worried about Bun

#270

Post by thot_experiment »

flother wrote: post #259
thot_experiment wrote: post #227

Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…

> Bun has no REPL Bun has a really nice REPL, can recommend https://bun.com/docs/runtime/repl

I am gonna check my sources better next time lmao, sorry!
Post reply on HN