I'm planning to do a stream in an hour or two from now

After a long, unplanned hiatus, I'll do a live coding stream starting in a couple hours from now.
Main topic will be a demo of some partially completed changes to the build system, and pushing forward on it a little bit.
Q&A will also be welcome from chat.

https://www.

twitch.tv/andrewrok/

In Bun’s zig fork, we added parallel semantic analysis and multiple codegen units to the llvm backend on macOS & Linux

This makes debug builds of Bun compile > 4x faster, improving internal development velocity

We do not currently plan to upstream this, as Zig has a strict ban on LLM-authored contributions.

kristoff_it 4 days ago
Bun has stopped donating to the ZSF after the Anthropic acquisition

the binary size shrinks by 3 MB - 8 MB, the benchmarks are between neutral and faster

The depth-of-recursion tests for TOML/JSONC parsers went from 25_000 -> 200_000 because Rust’s smaller stack frames (LLVM lifetime annotations let the optimizer reuse stack slots) mean 25k levels no longer reaches the 18 MB stack on Windows.

@**Chris Boesch** I just want to reassure you along with everyone else who is trying to contribute that you're not doing anything wrong. On my end the reason you might not have gotten any review feedback lately is:
* focusing on finishing my own build system branch for the 0.17.0 tag
* going on vacation for 1 week
* dealing with personal matters in my life

The other core team members have their own reasons for how much time they spend on the PR queue. As a reminder, nobody including myself has committed to any particular amount of time. It's all best effort, goodwill type of situation.

With that in mind, however, there's a greater discussion to be had here, which is also taking place on ziggit.

After the 0.17.0 tag, I plan to focus on improving the contribution pipeline. We still have a lot to discuss, both publicly and internally, but in general I'd like to try to create a higher trust environment, where more people have more capability to unblock each other and themselves without bottlenecking on ~4.5 active core team members. Furthermore I'd like to solve the technical problem of the frequent codeberg downtime - either by self-hosting or by choosing a different technology that is resilient to outages.

In conclusion if contributors are feeling frustrated right now with the review queue, code forge stability and performance, and similar matters, you're not alone. Let's come up with a way to increase contributor trust and autonomy without compromising the integrity of the project, both from software quality perspective and as a community of people looking to hone their skills and resumes.

I would have preferred to just continue cooking, but sometimes you gotta sharpen your knives