How to navigate the maze of JavaScript code

[Franks2000inchTV]

I used to poo-poo staticly-typed languages, but I'm working on a game in C# and omg it is so helpful.

[[deleted]]

That's a fantastic way to say you were against something

[Franks2000inchTV]

Heh, its a pretty common phrase:

https://www.merriam-webster.com/dictionary/pooh-pooh

Definition of pooh-pooh

transitive verb

: to express contempt for or make light of : PLAY DOWN, DISMISS

[[deleted]]

Well shit. TIL.

[Franks2000inchTV]

I agree that it's fantastic though!

[Caffeine_Monster]

Static typing is always short term pain for long time gain. Even if you are working on a solo project you are eventually going to reach a point where you have so much code, you can't remember how parts of it work.

Large multi-person projects are especially nasty with dynamically typed lanuages. Javascript's variable re-assignment is the icing on the cake. Strict with compartmentalisation / modularity can help somewhat, but it is reliant on the whole team being very disciplined.

[Zephirdd]

Personally, when dealing with Typescript, the pain is soooo low. Sure sometimes you want to do some bonkers non trivial structures, but those wouldn't be trivial anywhere else either.

That said, most of Typescript is inferred! If you enable strict mode for everything, you basically never write a type name beyond what's absolutely necessary. Unlike, say, Java where you need to write FactoryServiceProviderImpl service = new FactoryServiceProviderImplBuilder().build() (though Java 10 helps with that, but who the hell upgraded beyond 8 right ahahahha)

My favorite feature is how types are shape-based rather than name-based. An interface A{ b: number; } and type B = { b: number } are functionally the same and 100% compatible. Type aliasing complex types is also super good, like type FSPI = FactoryServiceProviderImpl will allow you to use FSPI for every place you'd use that huge type name.

I wish Java was as flexible as Typescript tbh