DEV Community

loading...

Discussion on: TypeScript is slow. What can we do about it?

Collapse
ivanjeremic profile image
Ivan Jeremic

I would claim that it is useless and unproductive more time is spent on finding types and fixing types than developing, good eslint setting and good editor are better that TS in my opinion, TypeScript and Types developed a hype similar to Apple products almost a Type fanbase who type everything everywhere and all he thinks is types types types, if you are one of there who use TypeScript to detect missing imports or underline unused variables and functions then you don't need TypeScript, this is also possible without it.

Collapse
alekseiberezkin profile image
Aleksei Berezkin Author

I hear this quite often about TS. However, IMO there's no controversy: if you feel you don't need types, you actually don't need them. Lucky you! Your editor is fast, and npm scripts are short. You are happy developer who've never worked in large old enterprises in its worst sense. Having types in such projects is usually the only good thing about them.

Collapse
ivanjeremic profile image
Ivan Jeremic

I'm not against types but it gets crazy if types are more code then my actual code, I'm for to only type what is really needed like what gets returned that's it.

Thread Thread
manitchanthavong profile image
Manit-Chanthavong

TypeScript pulled me back into Node.JS development. . Without TypeScript I would have ditched node and moved onto a different platform altogether.

IMO, developing with node, typescript, vscode is a whole lot faster and more enjoyable than asp.net core, c#, and vs. However, for large Node apps, there are some serious development patterns you have to be aware of to make your app successful.

Thread Thread
0916dhkim profile image
Donghyeon Kim

Same here. I would never have come back to nodejs if there wasn't TS.