Python Is Eating the World
The part that Python really bothers me, as someone who had write Python for almost 10 years, and right now doing it professionally, though personally I don&#x27;t consider myself a Python developer rather than a Python senior user, is actually obvious to nail down, and frustratingly, difficult to handle.<p>SLOW. The sin of all. I don&#x27;t want to make other arguments with people who just come to repeat &#x27;Oh you can make it fast, you are doing it the wrong way&#x27;. Sorry, I have heard that 100 times, now is sounds like bug-as-feature excuse to me.<p>Sorry, but Python is just slow. All the stuff people might bring up is just trying everything to bypass Python itself. Multiprocessing is hell to work with, buggy and unpredictable. Cython is OK but it is not Python.<p>Python&#x27;s slowness is like cancer, and terminally so. Down deep, it is because its overtly flexible&#x2F;loose type system, the never-going-away GIL, and prematurely exposing of C-API makes it almost impossible to optimize without breaking the existing compatibility.<p>And most importantly, I don&#x27;t think it is solvable, truth is the patches are so integrated, people already forget what problem they tried to fix in the first place and just live with it.<p>But it will haunt Python in long term though, people will be struggling with Python in performant production until they start reimagining a world that without Python. Maybe a better Python in that sense.