> Did anyone try to map this code back to the original codebase to see if this memory problem exists in the original codebase?
replyFWIW what is being discussed is not memory problems, it's breaking rust invariants (the unsafe code has to follow specific rules, e.g. annotate lifetimes properly).
A single million line commit overwriting all of main is pretty flashy and high profile. Anyone who was working in this repo previously can throw whatever the heck they were doing out the window. This isn't in a branch, this commit isn't marked WIP, this is now the committed, active, current state of the bun project. That's quite a statement to make, even if there isn't a blog post somewhere (yet).
replystrongly agreed, all of the flashiness is coming from the detractors. the port itself has been quite lowkey
replyBun being a high profile project, that has had visible conflicts with Zig over AI contributions, and was recently purchased by Anthropic, is naturally going to make something like this big and flashy regardless of the author's intentions.
replySo Jarred unintentionally “exploited” a marketing strategy by not making a big flashy announcement (?)
replyc’mon.