That's a stated goal, so nope. But releasing it before any cleanups is another story.

I'd also like to inform you that

- the current success metrics solely consist of their advertisement, my eyes looking at the code strongly suggest otherwise

- the Bun team lacks knowledge to actually make it more idiomatic: none of the Bun team has written any Rust and relying on model knowledge is already proven insufficient.

The release decision itself is presumably driven by that tbh. It's only LGTM from there when nobody knows how to review unsafe Rust.

▲

daishi55 a day ago | parent [-]

> the Bun team lacks knowledge to actually make it more idiomatic: none of the Bun team has written any Rust

Do you know how silly this sounds? Good engineers can work in any language. At the top companies (of which Anthropic is certainly one) they don’t have “C++ engineers” and “rust engineers” they just have engineers.

	▲	endospore 18 hours ago \| parent \| next [-]
		> Good engineers can work in any language Given that they are investing their time into actually learning the language before diving into this mess. No, unsafe Rust isn't supposed to be something you can handle without prior knowledge. Jarred was even asking in public how to use traits without runtime overhead during the rewrite. And the blog post phrased it like a normal problem to encounter while doing a million lines port... That's two months after the initial rewrite so you can guess if they learned.
	▲	simonw a day ago \| parent \| prev [-]
		One of the best Django engineers I ever worked with had hardly any Django or Python experience when we hired them, but had done plenty of Rails. They were up and running and super-productive with Django within a week.