I don't see any reason to use this over Deno.
Performance matters a lot.
Bun 0.3
11–20 of 64 posts
Re: Bun 0.3
#12I work on Bun
happy to answer any questions or feedback
Re: Bun 0.3
#13Would love to switch, but we're still missing the NodeJS TLS API
The “tls” module is on our list of node core modules to implement, somewhere near the top
Re: Bun 0.3
#14I work on Bun happy to answer any questions or feedback
I’ve built a few utility apps at work. I absolutely love it.
I hijacked your jsx support so that I had built in server-side templating without having to pull in any external libraries (e.g. React). The process of building my own TSX bindings was pretty trivial, but did feel like a hack (I created a React package.json entry that was a file path to my local source folder).
Is that scenario doable with less hackery?
Re: Bun 0.3
#15I don't see any reason to use this over Deno.
https://medium.com/deno-the-complete-reference/hello-world-p...
FWIW this similarly-trivial "Hello world" benchmark shows Bun's lead at ~25% faster than Deno at the moment, which doesn't seem insurmountable. https://github.com/denosaurs/bench
Re: Bun 0.3
#16I work on Bun happy to answer any questions or feedback
What are the things you are hoping to release in Bun v0.4?
Re: Bun 0.3
#17Would love to switch, but we're still missing the NodeJS TLS API
The “tls” module is on our list of node core modules to implement, somewhere near the top
Not that I want to cause scope creep, but it would be amazing to have something like the certmagic library (the Caddy team’s automatic TLS Go library) without having to reach for a 3rd party.
Re: Bun 0.3
#18I work on Bun happy to answer any questions or feedback
I’ve built a few utility apps at work. I absolutely love it. I hijacked your jsx support so that I had built in server-side templating without having to pull in any external libraries (e.g. React). The process of building my own TSX bindings was pretty trivial, but did feel like a hack (I created a React package.json entry that was a file path to my local source folder). Is that scenario doable with less hackery?
You can set “jsxImportSource” in tsconfig.json or jsconfig.json to point to a different jsx package
There is also a setting in bunfig.toml but it appears we haven’t documented it yet
Re: Bun 0.3
#19I work on Bun happy to answer any questions or feedback
Bun seems really cool! I had a question about this part:
> Bun now works in more Linux environments, including Amazon Linux 2 and builds for Vercel and Cloudflare Pages. (Previously, you might have seen errors like: "version 'GLIBC_2.29' not found")
How would building for Vercel and CF pages work? Like normal but installing the relevant build tools using bun?
Re: Bun 0.3
#20I work on Bun happy to answer any questions or feedback
I was curious where the 'dgram' module is on your roadmap?