DEV Community

Discussion on: Is TypeScript worth it?

 
jwp profile image
John Peters

For me, Typescript will always be the default tool, it's simply a better choice.

Thread Thread
 
ionline247 profile image
Matthew Bramer

For me, it doesn't provide enough value yet for me to implement it in any code base I'm working on.

Thread Thread
 
worc profile image
worc

the added complexity isn't subjective though. typescript increases the complexity of the language so it can handle typing and type errors. it's right in the name.

and, man, i don't know, if your workflow includes refreshing blindly and hoping that you've fixed your bug, typescript isn't going to save you. you need a much deeper level of re-education and tooling than just a type system to get rid of that bad habit.

Thread Thread
 
ionline247 profile image
Matthew Bramer

You're clearly wrong if you think I need a re-education of how to debug software. I don't run into these issues with the language because I've never relied on the falsehoods you're touting and learned the language without using training wheels.

Thread Thread
 
worc profile image
worc

that's an interesting paper, for sure. but it does kind of undermine the original point of saying typescript is less error-prone than javascript, right? neither typescript or javascript (or coffeescript for that matter) were associated with a higher or lower number of bug fix commits.