News for hackers. Stuff that matters.
Re:Why Python is Slow: Looking Under the Hood (2014) by anewhnaccount2 on Wednesday October 25, 2017 @08:02AM (#15549330)
This is too categorical. And also it fails to define when small stops being small (and so is easy to defend by moving the goalposts). Yes, these are real problems, but some of them have (partial) solutions. You can use one of the many solutions to write a C, C++, cython and so on extension. You can have type checking with mypy. You can produce executable with cx_freeze (not compilation, but compilation is more of a solution than a problem). You can create parallel programs using multiprocessing. (etc.)
Re:Why Python is Slow: Looking Under the Hood (2014) by weberc2 on Wednesday October 25, 2017 @08:24AM (#15549436)
Writing extensions in c/c++ largely negates all stated benefits of using Python in the first place, and I'm proficient in all three languages. Further, mypy is hopeful, but it's not quite there yet (lots of holes and bugs--notably no support for recursive types). Lastly multiprocessing for parallelism is a poor man's solution, and far from what I've become accustomed to in Go, Rust, etc. Python is a nice language and it pays my bills, but Go beats it at many of its own purported strengths, in my opinion.
Re:Why Python is Slow: Looking Under the Hood (2014) by hasenj on Wednesday October 25, 2017 @10:27AM (#15550367)
Using these solution makes the development process much more troublesome than it needs to be, thus defeating the whole point of using python.