4 ms·
Two immediate potential benefits: - Only one tool to configure, instead of many - Many tools revolve around parsing your code and generating an AST, then mani
by acemarke 6y ago
Two immediate potential benefits:
- Only one tool to configure, instead of many
- Many tools revolve around parsing your code and generating an AST, then manipulating / processing that AST (Prettier, ESLint, Babel, TS, Webpack, ....). That's a lot of extra processing that has to be done. In theory, doing all that processing _once_, and reusing the AST, would potentially run a lot faster.
- k__ 6y agoAlso, fixes in the shared libs would be directly available to the tools build on top.