Re:Complete Rewrite of ESLint
by h1fra on Monday November 28, 2022 @08:34AM
(#33773429)
it's even weirder to say that and then say that you will add jsdoc, use tsc and publish types = having the exact the same processes without having a .ts at the end ahah
[ Parent
| on HN ]
JSdoc comments are 100% JS while TS types are not. This means you will be able to run ESLint without a TS compiler while still having types for people who want them. It's also more future-proof for if/when JS adopts a type system that may or may not be compatible with TS.
This sounds like everyone wins except the people who are overly-dogmatic about TS.
Re:Complete Rewrite of ESLint
by EduardoBautista on Monday November 28, 2022 @09:16AM
(#33773862)
If ESLint were rewritten in TS, you would still be able to run it without the TS compiler, since it would already be compiled into regular JS when published to NPM.
Why should you be forced to deliver via NPM?
What about Deno or people using it in web-only contexts?
If they use ES-compliant modules, a build step isn't even required.
Once again, it's not that they don't have types, but the TS fanboys are now complaining that it's "not the right types".