31–40 of 86 posts
Despite the 1.0 release tag, given that it's written in Zig, which is super duper Alpha, I'd trust it only as far as I can throw a floppy with its source code.
I completely forgot it was written in Zig. Thanks for the heads up. I completely agree, I don't see how this can be labeled 1.0 release.
Why are we wasting time saying "Bun runtime" when "Buntime" is right there? The video is well done, and I'm fascinated that it's built on WebKit instead of V8. Good luck, Bun.team()!
Very nice project, not a tool I would use (I rarely use Javascript) but I like the design philosophy behind it, and the focus on performance and simplicity. I think the announcement video was a bit forced/awkward, obviously reading a prompt, professionally produced but maybe not the most efficient way to promote this tool for this team.
Earlier quoted context omitted.
Changes to Zig could force changes to Bun, and changes to Zig are all but guaranteed.
It could force changes to Bun _internals_, which doesn't really affect users if the Bun team does not want to break API.
Nearly totally unrelated, but what is with the recent trend of showing people talking to but not look at the camera? Do they save money that way? It drives me bananas and is just a distraction from the content being conveyed.. Altogether, with their obvious attempt at slickness, I find this video rather corny.
On my small website, Bun is twice as fast pnpm which is already much faster than yarn which is much faster than npm.
I do wish the "each speaker holds the bun while talking" bit was kept the whole way through
It'd be really convenient to have a decently fast backend runtime, but more expressive than Go and without the hassle of NodeJS
How different are the performance between Bun and Go ? It'd be really convenient to have a decently fast backend runtime, but more expressive than Go and without the hassle of NodeJS