I read this issue earlier this morning and kinda feel sympathetic towards Andrew. Bun’s rewrite to Rust has obviously impacted him (hence the “unlike Rust” comment). Whilst that part is petty, it does seem to be driving him to find a solution for Zig. Personally, I don’t think garbage collection is the right solution (1-6x perf impact), but even still, the fact he’s searching for one to improve Zig following one of its biggest negative events is commendable imho. Either way, will be interesting to see where he lands.

It’s so disingenuous to assume that Andrew is doing this because of Bun. Seriously man, do better Fil-C’s overhead isn’t due to GC. And the GC is like the least interesting part (it’s arguably not required) Bounds checks cost Fil-C up to 6x, but Zig already has a story for bounds checks. So this could be a super compelling combination

@dreamsofcode_io But is this garbage collection? I'm not an expert, but it doesn't look like GC

@dreamsofcode_io This uncertainty about the future direction of the project makes it impossible to use the language though. All this drama is going to kill the language if he keeps it up...

@dreamsofcode_io It won't be the default, it's just a build setting. Almost like asan but for production. Default zig builds remain unsafe

@dreamsofcode_io Y’all think all that Fil-C is is a GC ?!

@dreamsofcode_io the unlike rust jab is petty but the rewrite clearly lit a fire under him, spite has shipped more open source than funding ever has honestly

@dreamsofcode_io I don’t see the hoopla and crying about this. It’s an optional mode and it seems like a logical addition to zigs tooling. People can never just look at things rationally.

@dreamsofcode_io hold up.. didnt he say in his blog post against jarred that there is nothing wrong with zig? that its a memory safe language and that jarred was simply writing slop and using the lang wrong?? so if its all fine why add memory safety features? awkward... 👀😂

@dreamsofcode_io Hopeful for overall outcome, the language will become better

@dreamsofcode_io He changed it to: "introduce an actually memory safe (unlike borrow checking) compilation mode inspired by Fil-C"... He's actively regretting the decisions he's making

@dreamsofcode_io I think this is a good experiment, for a long it has been either Rust or non-memory safe C type system languages, to see a C like language attempt memory safety is a welcoming change.

@dreamsofcode_io Would be cool to witness an alternate to borrow checker for memory safety. IF, he gets to that.

@dreamsofcode_io x.com/nank1ro/status…

@dreamsofcode_io Idk but I'm following you after reading your replies. Nice to meet you.

@dreamsofcode_io he claimed the memory issues in zig bun was due to sloppy code and now he’s trying to find a solution to a problem he claimed didn’t exist? bro seems like an emotionally disregulated man who needs therapy instead of pivoting his project out of spite.

@dreamsofcode_io Also I think there are other good projects (like Ghostty) in Zig that will probably not see a rewrite in Rust.

@dreamsofcode_io You have it backwards. Zig is a solution looking for some problem to fix.

@dreamsofcode_io He needs to go seek help

@dreamsofcode_io garbage collection is likely never the right solution to anything. it's a bandaid for poorly made systems.

@dreamsofcode_io Absolutely