|
Hello, This is probably a question that was already answered somewhere in among all the issues/discussions in the main repo, but I couldnt find a clear one. If you're spending time on rewriting the whole linter, why not do it in Rust directly? Seems like a missed opportunity to get up to speed (literally) with 2025's standards (eg Biome). ESLint is amazing, but speed isn't its strong suit. However, Im sure there are good reasons behind the decision. At least we are getting built-in type-safety 👍 |
Replies: 2 comments 2 replies
|
I think the author answered this question in the interview at https://www.youtube.com/watch?v=m9Oo_hI4EjI, which is also the reason why it's not searchable. |
The decision is quite clear that eslint will be the most customizable linting tool in the market. |
|
See the extensive discussion here: |
|
I did and it was quite insightful, but there was no clear answer about it. The video is what I was looking for. |
I think the author answered this question in the interview at https://www.youtube.com/watch?v=m9Oo_hI4EjI, which is also the reason why it's not searchable.