Live data from Hacker News

Bun 1.4

bun.com

101–110 of 198 posts

Re: Bun 1.4

#101
post #56

I recently pivoted to Rust for the backend development, after getting tired of the nodejs ecosystem fragmentation and how fragile things feel. Bun seems very interesting since it allows you to do so many things without pulling in 3rd party libraries and bundlers? Is anybody using it instead of nodejs? how's the experience so far? I might have to give it a try. Yes, I know there's probably better options than Rust for…

The most appealing thing of Go to me is the good batteries including tooling. I don't use it much outside of little personal projects where I really don't want to deal with dependencies and want a small binary.

Yeah, I prefer Rust as a language but the ecosystem and toolchain is risky. E.g. build time scripts from upstream is too risky these days and it’s commonly used.

Go is a good stdlib and trivial build toolchain.

You just cargo build and all your apes gone.

Re: Bun 1.4

#102
post #33

I wonder what was total token cost of the rewrite.

I think around $300-400k, but that does not include the github issue/pr/ci stuff that runs continuously, which could double or triple it. Somewhere, the first two weeks were said to be about $200k.

That total assumes API billing rates, which isn't what Anthropic pays for the inference. So I'm confused why people keep quoting that. It's not representative of what it'd cost for you either because you could use cheaper models.

Re: Bun 1.4

#103
This was an incredible demo for Claude. The runtime hosted Claude Code for months and I never saw the slightest issue. Wholly machine ported. Truly amazing.

Re: Bun 1.4

#104
Hate to comment more on the drama, but it's only after watching Andrew Kelley's talk at Software Should Work [1] that I realized how philosophically different he is from Jarred and the broader SF AI/VC sphere. Here he is in a conference talking about agency, enshittification, and learning to deprogram from a deeply religious background and then using that experience of internal questioning to define his relationship with computers.

And somehow, the programming language he made (that currently bans AI contributions outright) ended up being instrumental for a tool that's in the center of the whole craze, and doing Tony Hawk 900 aerial spins with agentic AI software rewrites under a frontier lab. I'm not commenting on the effectiveness of the rewrite, but it seems fascinating that for a moment Zig found itself at the intersection of two very different camps that the software world seems to be divided into. It seems in retrospect like a bomb waiting to go off even if they didn't jump ship to Rust!

[1] https://www.youtube.com/watch?v=zLZwpH5lCD4

Re: Bun 1.4

#105
post #98

Earlier quoted context omitted.

The code is here https://github.com/oven-sh/bun/ go and audit all you want

The author didn’t care to himself, just merging enormous PRs with “lol” tweets about how github doesn’t display all the changes because there are too many. This is unmaintable mess, and the author himself is struggling already, given how he pushed the release date ten times.

> given how he pushed the release date ten times

Jared has always done that. Thats not specific to this 1.4 release.

Re: Bun 1.4

#106
post #94

Absolute crickets from the "there's no way LLM's can rewrite Bun to Rust this quickly, it's going to be buggy, it's marketing" crowd Comments here 3 months ago are quite something: https://news.ycombinator.com/item?id=48132488

this is currently on the front page of lobsters, I saw it even before I saw the bun 1.4 release announcement https://tipiirai.com/writing/bun-rust-rewrite-worries

Lobste.rs is now flagging Bun 1.4 post as spam and comments are dismissing it as nothing, even as that blog post got much more discussion and piling on about the rewrite.

Internet echo chambers are quite a problem. AI success and its immense implications are wreaking havoc on the ability of even intellectuals in HN and lobsters to face reality in front of them, even as their predictions become falsified again and again.

Re: Bun 1.4

#107

every couple years someone rewrites the whole toolchain and we collectively agree the last one was the mistake. good to know the cycle still works.

"Developing APIs is the process of building future regret."

- Chet Haase

Re: Bun 1.4

#109
post #78

Earlier quoted context omitted.

I would guess that many devs' preference would be for a larger standard library, but not a kitchen sink. Personally, I'd be happy with a larger suite of utility functions (say, most of Lodash / es-toolkit - remove the need for left-pad silliness), probably SQLite bindings (having a good persistence layer is great, it's perhaps the most robust and most widely deployed software on the planet), but not YAML (complex, se…

SQLite bindings should absolutely not belong in a JS "standard library". SQLite is a project that most JS environments won't have enbedded.

There should be a space between "in the standard library" and "in a library written by some random person with a github account". An sqlite driver does not need to be bundled by the runtime, but it would be pretty great if there was an official sqlite driver library developed and supported by the node.js project but distributed through NPM.

Re: Bun 1.4

#110
> Bun is not 100% compatible with Node.js yet. In practice, much of the existing JavaScript ecosystem just works.

I don't care about 100% compatibility. NodeJS is a standard but dead to me.

I rather have faster feedback loop and less development/build/test time than worrying about Node.JS compatibility.

Bun is the answer for my flow.

---

Bun might as well promote itself as the total replacement of Node.JS, and I will still hop in.

Post reply on HN