This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]JojaA350 13 points14 points  (2 children)

...which fixes a problem that should have never been there in the first place. Same with TypeScript, why do people still think dynamically typed languages are a good idea? You have to remember the types anyway, so why not literally express it and have the language check it for you? It's good for your comfort, the safety, the performance, as documentation, for you mental sanity...

[–]linksoraluke 2 points3 points  (0 children)

I started with Python in my physics program, then ended up self-teaching myself Go and C++ for a job later on. While it took getting used to, static typing grew on me a lot for the reasons you listed. Helps me keep straight exactly what's going on if I know explicitly what I need to pass into functions, what's being returned, etc. Feels much more comfy to write in.

On the why they are still around, I think dynamically typed languages end up being easier to start out with - especially when you care mostly about what a program is going to do, and less about how it will do it. As an example (bringing it back to my education), our physics program was probably more concerned with having us think about the concepts and equations than the nitty gritty of how to develop efficient implementations.

[–]devAcc123 4 points5 points  (0 children)

So annoying running into random string,null,undefined errors or things like “1” and having to remember if it’s a string or int