4 ms·
I don't dislike TS because I love JS so insult it all you like. Besides TS is just a superset of JS so it's still got all of JS's warts. It's just a glorified l
by arkanciscan 7y ago
I don't dislike TS because I love JS so insult it all you like. Besides TS is just a superset of JS so it's still got all of JS's warts. It's just a glorified linter.
I dislike TS because it provides no benefit to me. I already have a type checker, it's called a browser. I dislike TS because a bunch of people who wasted their time learning Java or C# are forcing me to deal with it because they can't do their job without a compiler to tell them how.
You need types, that's your problem, not mine.
- JamesBarney 7y agoIt's great that you always write bug free code, but then typescript was not written for you, it was written for the rest of us who write the occasional bug, refactor an API that we didn't realize another developer was using, or can't quite remember the order or shape of args that a library call takes that we only use once every 6 months.
- deleted 7y ago[deleted]
- arkanciscan 7y agoWhy don't your tests catch your TypeErrors? You do have tests don't you?
- Can_Not 7y agoTests aren't an alternative to types. They're better together.
- stevenwliao 7y agoWhy would you write a test instead of a type declaration if you had the choice?
- arkanciscan 7y agoTS checks at buildtime. It can't guard against runtime TypeErrors because JavaScript is a dynamic language (despite all the effort to "fix" that). Tests can catch all TypeErrors, TS can't. Why use two tools to do the job that one can do alone?
- ng12 7y agoI agree that the type checker isn't that useful but I still use TypeScript for two reasons: 1. Accurate autocomplete. 2. Typing my domain models so they play well with autocomplete.
- arkanciscan 7y agoThe first thing I do when I install an editor is turn all auto-completion off. Especially the auto-closing brackets. Drives me NUTS!