4 ms·
I mean... if it was me: 1) I know Rust, not Go (esbuild is written in go-lang) 2) I don't have to worry as much about breaking Rollup, and I'm not nearly as c
by swsieber 3y ago
I mean... if it was me:
1) I know Rust, not Go (esbuild is written in go-lang)
2) I don't have to worry as much about breaking Rollup, and I'm not nearly as confident in my ability to write performant JS as I am in writing performant Rust.
- Tade0 3y agoMy experience is that the main reason why Rust is faster than JS in some applications is that the latter tends to do a lot of copying and other memory-intensive tasks - especially those related to running the JS virtual machine. If you can reduce the problem to a series of operations on pre-allocated typed arrays, JS is fast enough. Unfortunately in the case of Rollup that would be hard to do.