this post was submitted on 18 Oct 2023
325 points (96.0% liked)
Programmer Humor
32396 readers
436 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
Might as well not use TypeScript
Just as irritating as seeing people use linters only to have a lot of files with @ts-ignore all over the place... Like why even bother?
oh you've got a private variable that I want to use? No worries, (foo as any)['secret'].
using
any
is actually much worse than using TS, because you're basically telling the compiler "don't help me here".. at least with JS the IDE is gonna help you.. :/That's the joke
tbh I don't remember why I'm using TypeScript
Cause otherwise it's plain JS :/
I don't follow, stamping every function with
: any
lets you merge the branch and deploy it... trying to properly type everything extends the initial migration time likely to a level where management just says no.Use a combination of
allowJs
andts-ignore
, do progressive enhancement, and convert your codebase file by file. Addingany
everywhere literally turns off type checking altogether codebase wide, including type inference. It also means a huge PR that's both just noise that needs to be fixed later, and messes with your git history (good luck getting anything useful out ofblame
orbisect
now).Just getting a green build doesn't mean things are okay. You're worse off than before doing that.
I disagree that you're worse off (the core of my comment was that even a shitty migration encourages better practices)... but I wasn't super familiar with TS hinting - using ts-ignore would be preferable.
Personally, I mostly work in PHP and we use a similar system. Strict typing is default off so we've slowly propagated
declare(strict_types=1);
to enable compile and runtime checking on a per file basis.