I work on Bun. Happy to answer any questions
I contributed to Bun one time for SQLite. I've a question about the licensing. Will each contributor continue to retain their copyright, or will a CLA be introduced?
Thanks
391–400 of 1001 posts
I work on Bun. Happy to answer any questions
I contributed to Bun one time for SQLite. I've a question about the licensing. Will each contributor continue to retain their copyright, or will a CLA be introduced?
Thanks
I work on Bun. Happy to answer any questions
Do you think Anthropic might request you implement private APIs?
I work on Bun. Happy to answer any questions
I work on Bun. Happy to answer any questions
This reads more like Anthropic wanted to hire Jarred and Jarred wants to work with AI rather than build a Saas product around bun. I doubt it has anything to do with what is best for bun the project. Considering bun always seemed to value performance more than all else, the only real way for them to continue pursuing that value would be to move into the actual js engine design. This seems like a good pivot for Jarred…
It doesn't read like that to me at all. This reads to me like Anthropic realizing that they have $1bn in annual revenue from Claude Code that's dependent on Bun, and acquiring Bun is a great and comparatively cheap way to remove any risk from that dependency.
My long-term bet on Node being "boring" and "stable" continues to pay major dividends. So glad I never invested any time and effort on this ecosystem…
Bun is such a great runtime. If you haven't tried it, try it. It's got bells and whistles. This will make sure Bun is around for many, many , years to come. Thanks Anthropic. Why Bun? Easy to setup and go. bun run Bells and whistles. (SQL, Router, SPA, JSX, Bundling, Binaries, Streams, Sockets, S3) Typescript Supported. (No need to tsc, bun can transpile for you) Binary builds. (single executables for easy deployment…
It'll be around until they realize it makes 0$, and costs them millions per year in salaries/stock. then it will quietly die