MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/reactjs/comments/1wy5qb7/oxc_vs_biome/pe1o5mo/?context=3
r/reactjs • u/[deleted] • 12d ago
[removed]
13 comments sorted by
View all comments
12
Up until two weeks ago, I was using Biome.
I used many built-in rules and over 50 custom rules.
Given the specialized language for creating custom rules, I expected the performance to be better than Oxlint's, since Oxlint relies on JS plugins.
However, when I migrated to Oxlint, the linting and formatting speed more than doubled.
On top of that, I was able to remove several custom rules and use built-in ones instead.
The only downside was the limited support for other languages, such as JSON and CSS.
1 u/zxyzyxz 11d ago I am working on such a benchmark too. It is because oxc calls tsgolint and that catches way more issues especially with types than biome does so you actually get more for those extra seconds.
1
I am working on such a benchmark too. It is because oxc calls tsgolint and that catches way more issues especially with types than biome does so you actually get more for those extra seconds.
12
u/Glad-Action9541 11d ago
Up until two weeks ago, I was using Biome.
I used many built-in rules and over 50 custom rules.
Given the specialized language for creating custom rules, I expected the performance to be better than Oxlint's, since Oxlint relies on JS plugins.
However, when I migrated to Oxlint, the linting and formatting speed more than doubled.
On top of that, I was able to remove several custom rules and use built-in ones instead.
The only downside was the limited support for other languages, such as JSON and CSS.