Re:We sped up bun by 100x
by nightpool on Thursday April 02, 2026 @03:57PM
(#47619410)
Seems like they actually sped bun up ~1x:
So you have to maintain a completely separate git implementation and keep that up to date with upstream git, all for the benefit of being indistinguishable on benchmarks. Oh well!
[ Parent
| on HN ]
> maintain a separate git implementation
If git were a rapidly evolving project then I'd think this'd be a stronger issue.
With git being more of an established protocol that projects can piggy-back off of from GitHub to jj, filling a library in a new language seems like something that contributes
[delayed]
This was orchestrated and developed by agents with verifications like the codebase compiling or git's CLI test suite passing.
That was so the commit authors don't all appear like blank accounts on GitHub
Surely "the commits are attributed to the user who creates them" is a pretty basic feature of the git CLI, and not something that you can add in as a fix later after posting your project to Github and writing a blog post about how much faster than git it is.
It's very easy to be faster than git's CLI if you don't have to do any of the things that git's CLI does!
I don't know zig well. What's raising flags for you?
The commit I linked shows that it didn't even read the user name and email from git's config file, but used a test name, which means it's woefully incomplete.
Then there's stuff like this: https://github.com/hdresearch/ziggit/blob/master/src/cmd_bra...
It's just one giant function. Sometimes big functions are necessary. This one is clearly AI generated and not very readable for a human. This is just from a quick glance.
Re:We sped up bun by 100x
by testdelacc1 on Thursday April 02, 2026 @04:40PM
(#47619877)
Now we just need that AI booster guy to join this thread and tell us that actually this is super impressive. He was doing that for that worthless “browser” that Cursor built.