Hacker News Reader

Comment by Destiner | Hacker News Reader

I don't see how they are going to compete with tons of ESLint plugins. There's just no way a small team can do such a large amount of maintenance.

View on HN

I don't need a ton of plugins, i need a working linter and formatter for js/ts and this job does rome for me.

I wasted so much time with configuration of eslint / prettier and a ton of plugins, that es why i had enough and switch to someting simpler... rome.

But if you want to configure every single bit of your source code, stay with eslint, prettier, ...

Most projects use the same set of the most popular plugins. Shouldn't be a problem to get those plugins ported.

You want to know how it competes? “yarn add rome”

Done.

Now demonstrate the equivalent using prettier, eslint, and typescript. It’s a configuration nightmare …

‘npm init @eslint/config’

As far as I can tell that doesn't include prettier which is an annoying configuration since eslint and prettier partially overlap in feature-set

That is true. It’s easier to get ESLint and prettier running together than it uses to be, but it is still a bit of a hassle. Prettier needs to be added as an ESLint plugin, and that allows all its rules to be defined in the ESLint config.

Feels like they could stand to merge, like eslint+tslint.

This seems to have worked for Ruff in the Python world: https://github.com/charliermarsh/ruff

It re-implements a bunch of popular linting rulesets & plugins in Rust and is incredibly fast, especially compared to the other tools.

Do you think LLMs and coding assistants (current or near future iterations) might change this?

Reply on news.ycombinator.com