Post

@bun.sh is gunning for @vite.dev! youtu.be/NvitRPQqaSs Now it can serve HTML files right off the command line, and it even supports API routes!

youtu.beIs Bun The End Of Vite?YouTube video by Jack Herrington

Dominik Zogg

@dominikzogg.bsky.social

4 Feb 2025

I like the Unix philosophy: Do one thing, do it right. Bun is the opposite. Feels like an upcoming vendor lock, even when its oss.

Jack Herrington

@jherr.dev

The community seems to want to go in the other direction with it. One tool to rule them all. Which, well, pros and cons.

4/2/25, 9:26 pm0 reposts0 likes

Dominik Zogg

@dominikzogg.bsky.social

4 Feb 2025

Biggest strengh of JavaScript is there is no monoculture. As long bun users are a minority its fine.

Jack Herrington

@jherr.dev

4 Feb 2025

Well, there is also Deno, VoidZero and Biome.

Dominik Zogg

@dominikzogg.bsky.social

5 Feb 2025

Vite and Vitest can be used separately. For me it's ok having one vendor with multiple tools fitting well together as long they can be used indepent. But bun mixes all up. S3 client / Built system / Runtime... Getting away from it once not beeing happy gets harder and harder.

Jack Herrington

@jherr.dev

5 Feb 2025

I feel yah. For example, the `Bun.serve` thing for me only goes so far as personal projects. To even consider it for production I'd want to factor the code so that there are no hard dependencies between Bun.serve and our IP code. So that if we wanted to move it wouldn't be a disaster.