I'm a little puzzled: Why should you care? The language in which Bun is written isn't part of its API, if you will. You care that you have something that does various javascripty things according to a particular spec of what it's supposed to do. If a bug is fixed in 1.4.x it's fixed, why should it matter, really, if that's in Zig or Rust?

▲

pier25 4 hours ago | parent [-]

Who in their right mind would immediately migrate their production apps into a complete re-write of a runtime?

It would be naive to think there aren't new bugs or changes in behavior introduced in 1.4.

▲

dgacmu 3 hours ago | parent [-]

(Well, the answer is "Anthropic, with claude code", but I'm not in possession of material information related to whether they are or are not in their right minds.)

But yes, of course there will be new bugs. But that's why 1.4.x for x > 0 is interesting. If the branch is being used and people are not reporting _more_ bugs, and the bugs you care about it are being fixed (successfully) on it, and it passes your tests, etc., ... I dunno. This is an application domain where you can do some pretty solid testing of it, comparative fuzzing, etc., so it doesn't strike me as entirely mad to jump over after a few minor releases where you can see the bug trajectory.

	▲	pier25 an hour ago \| parent [-]
		> Well, the answer is "Anthropic, with claude code" Anthropic is not exactly the hallmark of engineering excellence... quite the contrary. > But yes, of course there will be new bugs Obviously, which is why more thought should have been put into the transition. Not everyone will want to yolo their production projects into such a massive rewrite overnight.