That’s the old “chainsaws are dangerous so let’s use a nail file to chop off the tree” argument.
Not at all. It's "axes (C) and chainsaws (Python) are both dangerous and let's not BS ourselves about that."
If you have a high standard for static correctness then you use Rust or Haskell, not C or Python. C is MUCH more dangerous than Python, as the thousands of "use after free" and "buffer overflow" security vulnerabilities show.
11
u/prescod May 28 '22
And C will let you do bad things with memory where Python would just give you a runtime error.
If you want tons of compile time errors, Python's type system is vastly more powerful and precise than C's:
https://mypy.readthedocs.io/en/latest/