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

How is the Bun rewrite in Rust going?

lockwood.dev

Post reply on HN
Print view View original

311–320 of 412 posts

Re: How is the Bun rewrite in Rust going?

#311

Post by swiftcoder »

busterarm wrote: post #225
swiftcoder wrote: post #201

Earlier quoted context omitted.

> It was purely about maxing your compensation because changing jobs nets you more than promotions & raises. You don't view it as a problem that companies consistently compensate new hires higher than they are their experienced employees? Hell, I would have been perfectly happy to never change employers in my entire career to date, if my salary had anywhere near kept pace with my peers who were job-hopping.

> You don't view it as a problem that companies consistently compensate new hires higher than they are their experienced employees? It depends on the current employee and the incoming employee. They are not interchangeable cogs. Also not everyone consistently provides good value over their tenure -- a lot tend to work hard early and then for various reasons taper off. It's not necessarily their fault, but companies d…

> a lot tend to work hard early and then for various reasons taper off

And you don’t think that has anything to do with incentives (or lack thereof)?

> I've never been about comparing myself to others

Doesn’t have to be about comparing oneself to others. More about the cost of living increasing because software engineering salaries are rising around you…

Re: How is the Bun rewrite in Rust going?

#312

Post by thayne »

Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

That's not surprising. Claude code is buggy enough, and releases break things often enough, that I wouldn't expect users to distinguish bugs introduced by switching to rust-based-bun from the normal garden variety bugs.

Re: How is the Bun rewrite in Rust going?

#314

Post by denverllc »

thayne wrote: post #312
Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

That's not surprising. Claude code is buggy enough, and releases break things often enough, that I wouldn't expect users to distinguish bugs introduced by switching to rust-based-bun from the normal garden variety bugs.

I’ve come to just expect that my CC instance will randomly “blank” and that I have to resize my terminal / use page up/page down to get it to show again.

Supposedly they used a game engine to render their TUI but I’ve never had an FPS game do that.

Re: How is the Bun rewrite in Rust going?

#315

Post by throw1234567891 »

tomlockwood wrote: post #196
inglor wrote: post #179

Earlier quoted context omitted.

Take as long as you need to ensure software quality. A month without a release isn't a big deal and whomever needs a specific feature can offer to contribute or build themselves. Node has 4-6 weeks without a meaningful release (other than security stuff) pretty much every December. I think the criticism in the article is unfounded and whomever needed/wanted a release should have asked first instead of writing an "ang…

Author here: I don't need or want another Bun release or an NPM release or anything like that. Like I very clearly say in the article I just got chatting with a peer about the Bun rewrite and I decided to take a look. I'm consistently skeptical about new tech whether it is NoSQL or Blockchain or Serverless. Some of the things I'm skeptical about fail and some succeed.

That’s a great approach. No matter what you will always find a reason to be positively surprised!

Re: How is the Bun rewrite in Rust going?

#316

Post by brabel »

thaumasiotes wrote: post #305
brabel wrote: post #257

Earlier quoted context omitted.

But postmortem is literally “post death” in Latin. It’s synonymous with autopsy! I know people misuse borrowed words all the time, but come on?!

> But postmortem is literally “post death” in Latin. Sure, that's true. It's not really relevant to people who don't speak Latin. > It’s synonymous with autopsy! This isn't true. I have no idea how you got here. In English an autopsy is a surgical procedure performed on a corpse for the purpose of identifying the cause of death. In particular, it's a noun. "Post-mortem" in the etymologically literal "after death" sen…

An autopsy is an exam that is performed postmortem. And that’s really how people are using postmortem as a noun for the analysis that they perform after the “death” of a company, so it is a synonym at least approximately, if you don’t see that I guess you don’t have a very good imagination.

Re: How is the Bun rewrite in Rust going?

#317

Post by whyhnwhy »

thayne wrote: post #312
Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

That's not surprising. Claude code is buggy enough, and releases break things often enough, that I wouldn't expect users to distinguish bugs introduced by switching to rust-based-bun from the normal garden variety bugs.

[dead]

Re: How is the Bun rewrite in Rust going?

#318

Post by solid_fuel »

Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

[flagged]

Re: How is the Bun rewrite in Rust going?

#319

Post by bee_rider »

brabel wrote: post #257
interroboink wrote: post #189

Earlier quoted context omitted.

This might be terminology that's used differently in different places. For instance, in video games it is extremely common to use "postmortem" to mean "post-shipping." Example: https://blog.codinghorror.com/game-development-postmortems/ Note the dual emphasis on both "what went right" and "what went wrong," not just one or the other.

But postmortem is literally “post death” in Latin. It’s synonymous with autopsy! I know people misuse borrowed words all the time, but come on?!

The postmortem for many cows is “how did you like your hamburger” so it isn’t all bad (from the user point of view at least).

Re: How is the Bun rewrite in Rust going?

#320

Post by solid_fuel »

bendmorris wrote: post #238

As a comparison point, someone decided to try to fix the issues in the Zig original and is now claiming sub-second build times, plus fixed bugs, by modernizing the codebase and sticking with best practices - indicating that all of the issues that justified the rewrite were self-inflicted and addressable. https://ziggit.dev/t/buz-a-drop-in-replacement-for-bun-using... I have no skin in this game, and the Zig version i…

[dead]
Post reply on HN