Blog post: Why I'd Write a Linter in TypeScript #294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
3 tasks
JoshuaKGoldberg
commented
Oct 23, 2024
|
|
||
| ## More Thoughts | ||
|
|
||
| I've put a lot of thought into how linting plays into the web ecosystem. |
There was a problem hiding this comment.
Most of this section should be autogenerated IMO. I'd like to finish #67 before this one.
JoshuaKGoldberg
commented
Oct 23, 2024
| For experimental evidence, see the [Biome Linter rules from other sources](https://github.com/biomejs/biome/discussions/3) and [Oxlint Rules](https://oxc.rs/docs/guide/usage/linter/rules.html) pages showing _hundreds_ of community rules each linter has implemented. | ||
| I think that progress is great evidence that the drawbacks of rewriting lint rules in a new AST structure can be outweighed by other advantages. | ||
|
|
||
| ## More Thoughts |
There was a problem hiding this comment.
I was just sent https://nolanlawson.com/2024/10/20/why-im-skeptical-of-rewriting-javascript-tools-in-faster-languages/ and wow is this timely! Should mention.
Maybe in the 'straw man' section?
JoshuaKGoldberg
commented
Oct 23, 2024
|
|
||
| For experimental evidence, see the [Biome Linter rules from other sources](https://github.com/biomejs/biome/discussions/3) and [Oxlint Rules](https://oxc.rs/docs/guide/usage/linter/rules.html) pages showing _hundreds_ of community rules each linter has implemented. | ||
| I think that progress is great evidence that the drawbacks of rewriting lint rules in a new AST structure can be outweighed by other advantages. | ||
|
|
There was a problem hiding this comment.
Shoutout Dimitri for suggesting a section of what it'd take to convince me...
- An agnostic TypeScript backend service/daemon that makes types first-class-equivalent in Rust & others
- Rust becoming a standard part of web dev knowledge (unlikely)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Fixes #297.
Splits a self-contained post out of #284 on why I'd want a TypeScript-first core architecture.