4 ms·
If you deep dive into bun, it only has the gained performance for certain features and cant really even be compared to deno or node at the moment because it lac
by 12many 4y ago
If you deep dive into bun, it only has the gained performance for certain features and cant really even be compared to deno or node at the moment because it lacks so many other features that would better showcase its speed.
- treyhuffine 4y agoHere's a good summary that details your point on what Bun does well and where it lacks - https://levelup.gitconnected.com/is-bun-js-the-node-js-killer-ffeb0f89196a https://levelup.gitconnected.com/is-bun-js-the-node-js-kille...
- OJFord 4y agoHm, that claims SQLite is 'never' used for web backends; Bun says it's motivated for use 'at the edge' - first thing I thought of when I read that was Fly.io/Litestream: https://fly.io/blog/all-in-on-sqlite-litestream/ https://fly.io/blog/all-in-on-sqlite-litestream/ (No idea if there's any relationship between the projects, just makes me think that article's a bit dismissive.)
- gureddio 4y agoThis was the impression I got as well, but that instability was preventing some of the benchmarking from happening.
- jasonm23 4y agoI had a huge jolt away from the Bun hype-euphoria when I noticed it won't run Express. That level of incompatibility is the banner headline not some minor footnote, which is effectively how the bun team decided to communicate that little detail. If they're going to do things all-over-again...again in the JS community couldn't they get it right this time and go with speed, stability, compatibility... Instead of hype and cute mascots?