3 ms·

> If you're mostly worried about how quickly you can minify when you do minify, then you're worrying about the wrong thing. You don't need to be 'mostly' worri

> If you're mostly worried about how quickly you can minify when you do minify, then you're worrying about the wrong thing. You don't need to be 'mostly' worried about how quickly you can minify for esbuild to be the top choice- if you're only, say, 10% worried about build times and still 90% ('mostly') worried about size + execution speed, esbuild still comes out on top from these benchmarks.

capableweb 6y ago
Or, put in another way: If you're are 10% worried about that you get to do production deploys 10% faster and 90% worried about how fast you can deliver the code to your users when they load your site (and/or bandwidth costs that increases with each user), then esbuild might make more sense for you. For the rest of us that are 100% focused on the best experience for our users, we stick with the tools that does the best minification while being a bit slower, and throw more hardware at it if needed for the deploys.
- Griffinsauce 6y ago
  > throw more hardware at it And pay more. ESBuild is so much faster that I imagine it could have a significant impact on costs. Besides, yes you make a good point about the size savings scaling with users, but development speed compounds changes over time. The choice is a bit more nuanced than "smaller build always === 100% focused on the best experience"
- yoz-y 6y ago
  If you can do 10x the builds in a day, you can end up catching more issues before your users. Meanwhile the difference for them is in single digit percents. Interesting test to do next would be how performant are the compiled versions.
- wgjordan 6y ago
  > Or, put in another way: If you're are 10% worried about that you get to do production deploys 10% faster Correction: 10x faster, not 10%. The 60-minute deploy is shortened to 6 minutes, not 54 minutes. This is a significant difference in impact on a deployment workflow. > we stick with the tools that does the best minification while being a bit slower Correction: not 'a bit slower', _10 times_ slower, which is significant.

capableweb 6y ago

Or, put in another way: If you're are 10% worried about that you get to do production deploys 10% faster and 90% worried about how fast you can deliver the code to your users when they load your site (and/or bandwidth costs that increases with each user), then esbuild might make more sense for you. For the rest of us that are 100% focused on the best experience for our users, we stick with the tools that does the best minification while being a bit slower, and throw more hardware at it if needed for the deploys.

Griffinsauce 6y ago
> throw more hardware at it And pay more. ESBuild is so much faster that I imagine it could have a significant impact on costs. Besides, yes you make a good point about the size savings scaling with users, but development speed compounds changes over time. The choice is a bit more nuanced than "smaller build always === 100% focused on the best experience"
yoz-y 6y ago
If you can do 10x the builds in a day, you can end up catching more issues before your users. Meanwhile the difference for them is in single digit percents. Interesting test to do next would be how performant are the compiled versions.
wgjordan 6y ago
> Or, put in another way: If you're are 10% worried about that you get to do production deploys 10% faster Correction: 10x faster, not 10%. The 60-minute deploy is shortened to 6 minutes, not 54 minutes. This is a significant difference in impact on a deployment workflow. > we stick with the tools that does the best minification while being a bit slower Correction: not 'a bit slower', _10 times_ slower, which is significant.