Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> These days, TypeScript is effectively nothing more than a high-powered linter.

That's a bad take - typescript enables tooling like refactoring/navigation/completion that goes far above a linter. Development tools are just better with typescript vs JS.



That's ignoring all the negative effects of using typescript.


I was refuting the part about typescript (language and the implementation/language server) being a glorified lint - the value proposition is way higher than that.

Even other dynamic languages started moving in this direction due to the benefits of having type annotations brings to tooling/development experience overall.


The only thing you’ve listed was your preference for readability


True, I did not enumerate them. Adds another step to development and generally adds complexity would be other perceived downsides.

I'll note that most of the upsides are also subjective.


Deno/bun support TS natively, and Node is also adding support.

https://github.com/nodejs/node/pull/53725


> adds another step to development

I never understood this. It takes maybe 10 minutes to set up TypeScript in a project if you’ve done it before.

Compared to all the other times involved (time to learn typescript, time saved debugging and writing tests for type errors) the setup time is a total non-issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: