Live data from Hacker News

Bun 1.0 announcement [video]

youtube.com

41–50 of 86 posts

Re: Bun 1.0 announcement [video]

#41
post #7
post #3

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.

Fascinating, do you have literally any evidence whatsoever that this project doesn't work or isn't realiable?

A project can only be as reliable as its compiler. Zig currently suffers from a number of miscompilation [0] that is quite higher than for a more mature compiler.

[0]: https://github.com/ziglang/zig/issues?q=is%3Aopen+is%3Aissue...

Re: Bun 1.0 announcement [video]

#42
> One Bun enthusiast even wrote a plugin that lets you import Rust files into your JavaScript.

Oh wow, that sounds amazing. I would love an easy to way to use Rust crates from JS projects.

EDIT: I haven't been able to find that plugin or how it works, though. Looks like it's based on the esbuild pluing API?

Re: Bun 1.0 announcement [video]

#43
post #39

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

I’ve been playing with Rust as a web backend, and while I still feel really unsure about it, I’ve been surprisingly productive. With that, I occasionally run into some issue with async or lifetimes or pinning that really slows me down, though I’m unsure if that’s partly being a beginner.

Clojure is fairly interesting too, and it uses a similar async model to go.

Re: Bun 1.0 announcement [video]

#45

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.

Hopefully our careers in software work out because we will not be successful as actors. Actually Ashcon will be fine.

Indeed, he was definitely a natural :)

Re: Bun 1.0 announcement [video]

#48

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.

Changes to Zig can still be very significant. I found myself stuck between a rock and an hard place when I found out that:

- Zig v0.11 doesn't have async/await, which I needed, because they haven't implemented it yet on the self-hosted compiler;

- I couldn't use v0.10 due to some bugs with comptime in the old compiler, which are solved in v0.11.

Still, while bold, I don't think it's totally unwarranted to tag Bun 1.0. They may have to put some extra effort here and there to work around the language's instability.

This is not a critique of the Zig team, they make it very clear that the language is not ready for production use yet.

Re: Bun 1.0 announcement [video]

#49

Earlier quoted context omitted.

It could force changes to Bun _internals_, which doesn't really affect users if the Bun team does not want to break API.

I’m just not sure how you guarantee no changes to the API without knowing the size or scope of changes that may come to the language it’s built on.

As an example, Java does just fine at guaranteeing its own semantics completely independently of what happens to C++.
Post reply on HN