this post was submitted on 18 Oct 2023
327 points (96.1% liked)
Programmer Humor
32473 readers
557 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a good way to get started, and then incrementally type as much as you can, preferably everything.
Later on, or if you start a new project with TypeScript, it's a good idea to turn on
noImplicitAnyand only allow explicitanyin very specific framework level code, unit tests or if you interface with an untyped framework.The hassle really pays off later.
But if your code ever integrates with javascript you still need any everywhere so it's pretty pointless
Not true, in the absolute worst case,
unknownis what you should be reaching for, but it's pretty rare that you can't create some kind of type to interface with JS if it's not already got types. You can even use jsdoc comments as type hints in the JS too if you own that code.My not particularly hot hot-take: There's basically no legitimate use case for
anyapart from "I don't have time to type all this now, because I'm converting a massive project from JS to TS"There are some cases where
anymust be used instead ofunknownbut they usually involve generic constraints and seem more like a bug than intended behaviorAh you're right there, and I also agree, that feels more like a bug than by design