When I read about the bun rewrite I thought no sh*t, those are the exactly the types of bugs I would expect when doing a line by line rewrite of a program in a GC language to memory managed.

I was unimpressed with the engineering from the blog, and I'm not surprised to read andrew say they claimed no fuzz testing. I know someone who interviewed at bun when it was less than 10 people (around 5 he said). Allegedly jared lowballed the fk out of my friend, claimed they had no money because they're a startup, then proceeded to offer <1% equity

▲

outpost_mystic2 3 days ago | parent [-]

I think I'm missing something; neither zig nor rust are GC languages. Did bun originally start off in javascript or something, and the rewrite you're referring to is from JS to zig?

	▲	JurassicTyler 3 days ago \| parent [-]
		First line of the original article (not including the disclosure) > Bun started as a line-for-line port of esbuild's JavaScript & TypeScript transpiler from Go to Zig Then proceeded to talk about use after free bugs, leaks, and other things that wouldn't exist in GC written programs. Ironically, my friend jared lowballed is an expert in C, runtimes and threading