3 ms·
Incidentally this can come into play even for exceedingly popular packages. For example, consider deciding to use Babel versus TypeScript for ESn -> ES5. I am a
by kylecordes 8y ago
Incidentally this can come into play even for exceedingly popular packages. For example, consider deciding to use Babel versus TypeScript for ESn -> ES5. I am a fan of both, for different reasons and uses. Both are excellent tools, widely used, of great quality.
Babel, configured in a typical way, will have at least hundreds of (transitive) dependencies. TypeScript has none, every line of code is from Microsoft.
I have pointed this out to numerous people in the process of deciding between these tools; so far I don't think a single one has given this consideration any weight in the selection.
- true_religion 8y agoI give it a lot of weight. Microsofts releases are backwards compatible in many cases, and when not, they always have a detailed transition path. Their changes are never motivated by having to change to suit an upstream packages new version, and their entire codebase is cohesive. Its what I like in a compiler: a stable tool that I never worry about.