Hacker News Reader

The JavaScript tooling ecosystem is fragmented, bloated and slow. Rome is the best - and currently only - bet to fix this. I’m excited!

View on HN

Why do you think this is the only bet? What about things like Snowpack, Vite, and Esbuild?

Those are all great bundlers/dev servers but they aren’t as ambitious as Rome. Rome aims to be the one tool that handles everything: compiling, bundling, testing, linting and everything else.

You can also do that with Deno: - Built in testing library - Lint with `deno lint` - Bundle with `deno bundle` - Format with `deno fmt`

And it will be the one tool that handles everything poorly. Linting (eslint) and testing (jest) are solved problems, there's no way I'll migrate to Rome for these. They should focus on bundling which is the current pain point (although my bet is more on esbuild).

bad examples - the better one is Deno.

How will Rome be faster than the other tools when its also written in Typescript? I see that unification will be an advantage but I dont think it will be faster than others. Especially when native code/wasm based tools are already available. (esbuild/swc/rslint)

The positives I see are: - No fighting with different versions of different tools when upgrading - Simpler configurations

But I dont see any other reasons to convince people to use Rome.

Reply on news.ycombinator.com