4 ms·
Python folks with their strong + dynamic typing: (O.O') I will say from exp. that @anyfoo has a point. In the end, even webapp backends are clients, worker nod
by yingw787 6y ago
Python folks with their strong + dynamic typing: (O.O')
I will say from exp. that @anyfoo has a point. In the end, even webapp backends are clients, worker nodes within a much larger system infra. Anything that has to do with data that isn't a pass-through entity ideally should be both strongly and statically typed.
- dnautics 6y agoThere's another way to deal with it - which is to make crashes not matter. That's actually I would argue even better because you're already coding for robustness.
- lmm 6y agoPython has things that it calls "types" but they're not types according to the standard definition of the word (true types are associated with terms in a language, not with runtime values). And while a runtime error is far better than silent data corruption, it's a poor substitute for a build-time error.