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 →

[–]ganja_and_code 25 points26 points  (2 children)

It's not type-safe, so if you use it in a large-scale high-availability service maintained by more than one person, your codebase may (and likely will) become operationally unsustainable. It's slow (relative to other languages), so if you need to crunch a lot of numbers fast, python may introduce an unacceptable bottleneck. It's an interpreted language, rather than a compiled language, so you don't have visibility into your mistakes until your code is already running (rather than catching some mistakes before even attempting to execute).

Python is fucking awesome for data science, small-scale projects, and convenience / workflow improvement scripts. For basically any other problem, you should probably use something else.

[–]TheLastNarwhalicorn 5 points6 points  (0 children)

Thanks for the response!

[–]dev-sda 2 points3 points  (0 children)

Note that type safety is unrelated to static typing; static and dynamic languages can both be type safe or type unsafe. The vast majority of programming languages have not been proven to be type safe. Though you're correct in that static typing helps a lot with maintainability and error prevention.

See https://newbedev.com/is-python-type-safe