Live data from Hacker News

Bun 1.4

bun.com

181–190 of 198 posts

Re: Bun 1.4

#181

Earlier quoted context omitted.

Well if you ignore all the issues and declare victory, I think you’ll find it’s possible to decide anything is fine.

I really am curious about the issues that I'm ignoring twitter was a dumpster fire before and now it is (to me) less of a dumpster fire. so far it seems like the bun rewrite is going quite well. I haven't found any major issues since the merge despite, robobun being the top committer in the repo.

> twitter was a dumpster fire before and now it is (to me) less of a dumpster fire.

This gives your response away as completely non-serious. You can go troll elsewhere.

Re: Bun 1.4

#182

Earlier quoted context omitted.

~3 months start to finish and the price of 1 engineer for a year, to rewrite a critical infra codebase that tens of millions of user software relies on . Truly the goalposts keep moving. This kind of project would've have been 10x the effort and price a few years ago.

It's likely much closer to that price if you don't calculate with subsidized token pricing.

Once a model like Fable/Mythos is trained, that was used for this project, the inference costs are profitable. CapEx vs. OpEx. Every new Zig->Rust port of this caliber using Fable/Mythos costs the standard token price, it's not subsidized. The model already exists for the original CapEx, you can do 1,000 ports of this for standard token pricing.

Re: Bun 1.4

#183

Earlier quoted context omitted.

Well if you ignore all the issues and declare victory, I think you’ll find it’s possible to decide anything is fine.

Best to stand on an aircraft carrier, that really sells the message.

> Best to stand on an aircraft carrier, that really sells the message.

Can't do that anymore though, they keep having "laundry fires".

Re: Bun 1.4

#184

Earlier quoted context omitted.

Plenty of people on that list maintain serious production systems or open source projects in use by a wide variety of people. It's not just some nerds tinkering in their basement.

I don't doubt this is the case. Even if they're producing code by hand, surely they have LLM helpers by now. Coding agents have really only taken off in the last 10 months. So it is still early.

> Even if they're producing code by hand, surely they have LLM helpers by now.

Nah. Most of my coworkers got so annoyed by VS Code injecting copilot and other "helpers" that they have switched to Kate or Vim.

There are still a lot of places that value engineering excellence, and plenty of people who value doing the actual work and knowing that it is correct, instead of delegating to an LLM and hoping.

Re: Bun 1.4

#185
post #26

This is a huge win for Bun & Anthropic. I've been keeping an eye on Bun development cycle since they announced the Rust rewrite and the huge drama and backlash it generated. They seem to be proving the skeptics wrong with this release.

What exactly has this update led this to be a "huge win"?

I fully AI-driven rewrite of a massive codebase from one language to another within a reasonable release-cycle has never been done before.

There was a lot of sentiment around the lines of:

- Bun is done for, it's all slop now

- there's no way a fully AI-written codebase can work

- Jarred is an idiot for trusting AI to rewrite the whole thing

- they're never going to release this, there's going to be a billion of bugs

This release proved all of this wrong. It also serves as a great advertisement of how capable Anthropic models and harness are to enable this.

Re: Bun 1.4

#186
post #119

Earlier quoted context omitted.

[flagged]

Is it slop if the product is working as intended? I don't use Bun, so I don't know if quality has degraded. But if it hasn't and they're shipping features users want faster than ever, I wouldn't call it slop. I don't care who wrote the code if the end product is working.

We’re just three months in and already there’s plenty wobble.

Bun 1.4 Rust rewrite is not looking good https://news.ycombinator.com/item?id=49357401

Re: Bun 1.4

#187
post #185

Earlier quoted context omitted.

What exactly has this update led this to be a "huge win"?

I fully AI-driven rewrite of a massive codebase from one language to another within a reasonable release-cycle has never been done before. There was a lot of sentiment around the lines of: - Bun is done for, it's all slop now - there's no way a fully AI-written codebase can work - Jarred is an idiot for trusting AI to rewrite the whole thing - they're never going to release this, there's going to be a billion of bugs…

I don't think this release definively proved all of this wrong, no.

Re: Bun 1.4

#188
post #23

Earlier quoted context omitted.

I saw a post recently about how LLMs are much more effective in Ruby on Rails because it's batteries included, so you don't get so many implementation details crapping up the context window. I assume the same benefit applies to humans as well!

I am not into the Ruby on Rails world, but I find LLMs much more effective with powerful type systems like Typescript. Especially if you nudge it to keep things strict and (statically) eliminate invalid states. Do they use similar systems (build-time typing) for Ruby? When the LLM can verify its own output by running static analysis they produce better results. They also seem to understand type definitions and avoid…

Elixir started adding a type system as well after Typescript proved to greatly help AI feel confident in its output.

So yeah others are catching on the importance of a type system to enforce that successful contract for AI agents.

Re: Bun 1.4

#189
post #27

Announcing that the SSR memory leak is gone as part of a product launch is wild.

If it was one memory leak, it would be meh in the fix list, but the fact they've announced that they've eliminated all memory leaks because of Rust in about eleven days that's what's wild to me.

We are living in a new world when it comes in how software is prompted into existence.

Re: Bun 1.4

#190

> 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…

Yeah, I'm more interested in them covering the majority of people's needs and use cases than I guess having a hundred percent compatibility with libraries I'll never use.

I'd much rather it be a focus that I could run bun in serverless, sandbox, wasm, or workerd-like environments for agentic workflows where bun is the runtime to power additional functionality for AI agents.

I assume this is why Anthropic purchased them beyond just a PR stunt and where the project is going.

Post reply on HN