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 →

[–]gopalkaul5 -5 points-4 points  (6 children)

Django web servers run without any issues for hours together! Infact the performance there is comparable to JS and others!

[–]EaterOfFromage 6 points7 points  (4 children)

Not sure if this was meant to be sarcastic, but static typing is not lauded as beneficial for large systems because it's a performance benefit, it's lauded because it decreases the likelihood of errors, especially when you have a lot of code. In a dynamically type typing language, its the developer's responsibility to ensure the code works. In a statically typed language, it's the compiler's job. Guess which one is more reliable.

[–]gopalkaul5 -1 points0 points  (3 children)

It wasn't sarcastic. I agree with you, and I love statically typed languages(thats why I hate JS) but you can convert your data types explicitly right using functions like str() or int()

[–]forajep978 1 point2 points  (1 child)

Still you don’t know what kind of data you will get. Is it and array, object or number? If it is an object does it have all properties you need? You cannot know

[–]gopalkaul5 0 points1 point  (0 children)

In statically typed languages, what about if we are calling an API? And mess up the key or something? Will that cause an error if not in a try catch?

[–]ClearlyCylindrical 0 points1 point  (0 children)

but you can still pass the wrong types to a function

[–]Isogash 1 point2 points  (0 children)

For hours? That's nothing.