Hacker News Reader

Comment by notnullorvoid | Hacker News Reader

Projects like Biome and oxc seem to focus so much on reimplementing rules from eslint and broader eslint ecosystem vs. creating a plugin system for custom rules.

It makes those linters virtually impossible for many projects to adopt.

Seems like it's part of some larger anti composable tools trend that I really don't understand.

View on HN

My experience in the Python world is that the vast majority of projects only need one or two plugins for their linter, if any. Ruff has implemented so many flake8 plugins that I'm sure it has covered 99% of projects' linting setups.

In the JS ecosystem I've seen a fair share of custom rules developed internal to engineering orgs. Someone submits a PR a couple times with the same mistakes and it's easier to write a custom rule than it is to keep reminding them and possibly others to come.

This. At my workplace, we have so many custom rules because of the same mistakes.

I’m sure this isn’t an original idea but are any of these working on possibly translating JS based rules into rust or assembly and executing them faster?

You mean automatically translating existing eslint rules written in JS to rust? I haven't heard of any such plans, it would likely be really difficult.

That being said they would still need a plugin system (probably using wasm as compile target for plugins) for this to be feasible.

Reply on news.ycombinator.com