3 ms·
Just to clarify, Bun isn't a wrapper around V8. It's a wrapper around JSC. I don't think Jared's benchmarks were benchmarking Bun and Node so much as V8 and JS
by eatonphil 4y ago
Just to clarify, Bun isn't a wrapper around V8. It's a wrapper around JSC.
I don't think Jared's benchmarks were benchmarking Bun and Node so much as V8 and JSC.
I don't think benchmarking Bun against justjs is going to change much.
- SahAssar 4y agoConsidering the performance difference between node, deno and justjs I don't think that's right. There is clearly a big difference between different wrappers and how to handle different things. For example some of them delegate most of HTTP handling to a native lib while IIRC node does a lot of that in its js stdlib.
- jesse__ 4y agoFWIW I read it as the opposite. I think most of the stuff he benched was explicitly not benching V8 against JSC. This is all me reading between the lines .. maybe you know more about JS runtimes than I do and can confirm/deny my theories? Package manager perf: Bun (presumably) wrote a C++ or zig package manager that's integrated, and speaks NPM. I guess you could aruge that this benches their fast one against the npms V8 runtime, but.. that's a bit of a stretch for me. Copying large files: I'd be surprised if any of the benched distributions rely on the javascript runtimes to copy files on disk. HTTP Requests: Maybe distributions actually call into JSC/V8 for these .. I have no idea. I'd guess not, but this one sounds the most plausible case for "benching V8 against JSC".