2 ms·
Based on the title, I expected more from this. It's not so much "migrating a javascript project" as it is "marketing material style compare/contrast". Not tou
by horsawlarway 1y ago
Based on the title, I expected more from this.
It's not so much "migrating a javascript project" as it is "marketing material style compare/contrast".
Not touched at all is the actual migration process for any real project. Costs, upsides, problems, headaches, etc.
And ultimately, the sales pitch basically boiled down "it's faster because rust/threads". Which... is fine I guess, but just not all that compelling.
Prettier and ESLint are plenty fast in the sense that they process the file I just saved faster than I can react. Anything else I'm going to push off to CI anyways, where the difference between 10 seconds and 1 second is pretty meaningless.
So speed is great and all, it's just WAY down the list of things I actually care about. Show me the reduced config files after migrating a real project, or the reduced time copying boilerplate for configs. But... it doesn't look that exists based on this article, since it's basically just "ESLint and Prettier configs combined".
Why even show me the discrete lint/format steps if the whole pitch is that the tool combined them? Just show me the check command.
---
As a tool, this looks fine - would love to see a real successor to Rome, including the bundling step.
Otherwise this is a pretty bland & boring marketing pitch.