| ▲ | CrimsonRain 9 hours ago | |||||||
Bun "contributor community", that provides significant amount of code contribution, is largely non-existent. Almost all of the work is done by Jarred and others at Oven. If someone still wants to contribute, they can do so on Rust. There is no reason to give warnings and plenty of time just to delay something like this when doing it rapidly is possible (now with AI). Bun "user community", is not affected by this at all (yet) except the ai doomers/zig fanatics. When v1.4.0 is fully released, and if Bun team can't get it to full feature (and no new serious bugs) parity with last zig version within a few versions (let's say v1.4.2), then there will be real effects. I will be testing v140 after release. As a bun user community member, I expect no new type of crash, slightly faster perf/less memory usage and move on with my life. A rewrite like this is unprecedented but doesn't mean impossible. I am cautiously optimistic. | ||||||||
| ▲ | jdiff 9 hours ago | parent [-] | |||||||
This statement of a lack of community is at odds with the plentiful pull requests that were open before the rewrite. This is, as you say, unprecedented. Not impossible, cautious optimism is a fine response. But to bring back a point I made earlier in the new old light: Then let's be cautious. Let's do some announcements ahead of time. Let's get some people in and get some physical hands on the codebase. Let's not go from "Stop freaking out, it's just an experiment!" to a silent merge to main in a week. That causes reduced trust in the project from those even just a hair less optimistic than you, and that's clearly unhealthy for the project no matter how you define "the community." | ||||||||
| ||||||||