esbuild uses Go and concurrent algorithms which result in it being a performant tool. While it does support WASM as a host environment, that is not correlated (AFAIK) to esbuild being fast. It’s fast because it only uses V8 / node for resolving plugins.
It’s much easier to beat V8 / node performance metrics if you are building on Go, etc. and leveraging concurrency. As it turns out, most tools in the node ecosystem are built on top of node and therefore V8 which means performance will be hindered and concurrency will be hard to reason about.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for this write up, esbuild is awesome! It's blazing fast because under the hood it uses WebAsembly. I've been impressed with its performance.
My pleasure.
esbuild uses Go and concurrent algorithms which result in it being a performant tool. While it does support WASM as a host environment, that is not correlated (AFAIK) to esbuild being fast. It’s fast because it only uses V8 / node for resolving plugins.
It’s much easier to beat V8 / node performance metrics if you are building on Go, etc. and leveraging concurrency. As it turns out, most tools in the node ecosystem are built on top of node and therefore V8 which means performance will be hindered and concurrency will be hard to reason about.