Programmer Humor

32000 readers

1744 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

[email protected]

328

Me, migrating my code from JavaScript to TypeScript: (lemmy.world)

submitted 11 months ago by [email protected] to c/[email protected]

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 86 points 11 months ago (6 children)

Might as well not use TypeScript

[–] [email protected] 42 points 11 months ago (1 children)

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?

[–] [email protected] 7 points 11 months ago

oh you've got a private variable that I want to use? No worries, (foo as any)['secret'].

[–] [email protected] 11 points 11 months ago

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.. :/

[–] [email protected] 10 points 11 months ago

That's the joke

[–] [email protected] 3 points 11 months ago (1 children)

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.

[–] [email protected] 7 points 11 months ago* (last edited 11 months ago) (1 children)

Use a combination of allowJs and ts-ignore, do progressive enhancement, and convert your codebase file by file. Adding any 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 of blame or bisect now).

Just getting a green build doesn't mean things are okay. You're worse off than before doing that.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago)

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.

[–] [email protected] 3 points 11 months ago (1 children)

tbh I don't remember why I'm using TypeScript

[–] [email protected] 3 points 11 months ago

Cause otherwise it's plain JS :/

[–] [email protected] 2 points 11 months ago (1 children)

Forreal. Even a bespoke inferred return type is better than any 9 times out of 10.

[–] [email protected] 4 points 11 months ago

This is the only reason I haven't pushed my team to switch. I'm worried too many of them will be OP.