>>The stories about teams that were able to go down from N servers to 1 server by switching from Python to Go/Scala/node.js will hurt it in the long run. concu

>>The stories about teams that were able to go down from N servers to 1 server by switching from Python to Go/Scala/node.js will hurt it in the long run. concurrency designs and architecture play a greater role than the language , most of the times. Bottle-necks are often in bad-sync patterns , data-structures or overall designs. Language plays the role for semantic verification,formal models (for model-comparison...) ,type-system designs , proof systems etc .GIL is just one! Can't compare language vs another. After which the buck passes on to underlying implementation but cpython in our discussion is only thrown as a reference implementation and for production grade interpreters we might have to look outside like one by enthought. However language's built-in patterns to help advertise concurrency is another question altogether.