moot✳
A little more connected.
Join Moot

still thinking about this.

we need to finish node compatibility and there’s plenty of open issues to fix + threads but after AOT ships and is good, what other large new thing would we add to future versions of bun?

I don’t know. I never thought we’d actually do all this stuff.

Jarred Sumner@jarredsumner

a growing part of how I feel about bun is

this whole category of software - linters, formatters, package managers, type checkers, test runners, bundlers

this used to be hard software to build and now it can be prompted into existence in a day or two

View on X
#bun#javascript#runtime#aot#nodejs#roadmap
1
9 comments
9 comments

After the Series A, seemed like we’d only have the bandwidth to add & maintain a linter + formatter after growing the team by another -5 engineers - but being more than like 15 people with $0 in revenue and no progress on commercialization seemed crazy to me.

Adding a TypeScript type checker and ahead of time compiler to Bun wasn’t something we seriously considered until like a month ago.

bun is becoming the ultimate runtime. I wish AI agents would use bun more than python for their ad hoc scripts. Especially in cases where performance matters.

I wish Cloudflare had bought them and added it to workers.

I am not sure. Jarred seems to be doing good at anthropic judging purely from his posts. Not sure if cloudflare would have been able to provide the tokens necessary for all of these features

Fork JSCore and double down on full program optimization. Making TS really fast seems plenty work for another year.

Compiling OC currently needs 380GB which makes build farms difficult 🥲

omg 380 GB is insane

there must be some O(n^2) stuff going on. I would expect like 16 GB at the very, very worst. Will investigate