Seems to be working just fine though?

And like, this is just the beginning of the port. They did a mechanical port basically line by line, next step is to make it idiomatic rust.

I thought by now people would’ve learned to stop betting against this rewrite.

▲

cube00 a day ago | parent | next [-]

> Seems to be working just fine though?

As with all transpile ports, the true test will be how well it can be extended and maintained over time. Historically working with the output of a transpile is not pleasant and requires heavy rework to get it to the point where you can be comfortable enough to extend it.

The existing community is now either going to need to learn Rust or new Rust developers are going to have to join the project and they may not invested enough to refactor the transpiled output when they could work on something else like Boa.

▲

daishi55 a day ago | parent [-]

historically we didn’t have LLMs which don’t mind “unpleasant[ness]” and “heavy rework”.

This is I think a preview of the future of software development. LLMs are having the same effect as compilers, frameworks, etc - they are making new kinds of software development feasible which were not previously so.

	▲	benrutter a day ago \| parent [-]
		> historically we didn’t have LLMs which don’t mind “unpleasant[ness]” and “heavy rework”. I'm not quite as optimistic. "Unpleasantness" might sound like subjective disgust, but it often relates to objective criteria like complexity, that increases the surface area open to bugs in a real way. Similarly, if reworking has a non-0 chance of bugs, its gonna have some form of risk, and a major one will of course be higher. LLMs may be capable of a lot, and they miggt change what projects people can take on, but they definitely don't write bug free code. The bun rewrite/transpile did use some neat ideas like lots of testing and per-file translations, so hopefully they have more in their toolbox than "LLMs hopefully won't be affected by complexity or write bugs"

▲

endospore a day ago | parent | prev [-]

> next step is to make it idiomatic rust

You can tell what will happen when they release it before sorting out all the new bugs introduced by the not-exactly-line-by-line port.

▲

daishi55 a day ago | parent | next [-]

Sorry you think they’re not going to continue developing and improving bun and making it more idiomatic?

Given the success of the port so far and the fact that CC is now running on rust Bun, that seems highly unlikely to me.

▲

endospore a day ago | parent [-]

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.

▲

kccqzy 20 hours ago | parent | prev [-]

But Bun did not even release a new version of Bun written in Rust yet. It was still a canary version.