search

GoogleChromeLabs / tooling.report

tooling.report a quick way to determine the best build tool for your next web project, or if tooling migration is worth it, or how to adopt a tool's best practice into your existing configuration and code base.
https://tooling.report
Apache License 2.0
847 stars 49 forks source link

Scores should also include perf and bundle sizes in addition to just features. #397

Closed ermish closed 3 years ago

ermish commented 3 years ago

Title says it all.

Feature comparisons are helpful, but results should also be compared. For example, if one tool builds twice as fast or produces much smaller bundles, it should be a significant key decision making point 👍

surma commented 3 years ago

We are consciously and actively excluding things like build time from the scoring, as outlined in the About section:

“Tests should be user-centric. The production impact of DX (build times, hot reloading, etc) is indirect and often subjective, so these are not currently represented.”