To those trashing Python in favor of Golang: A compiled language with no OO is not a replacement for Python.
Why?
I mean, come on. Who in their right mind would ever claim that Go is not a good choice to develop web services?
And are we supposed to turn a blind eye to Python's problems such as sub-par performance and the GIL?
I understand how Python fanboys will pick Python over alternatives whether that makes technical sense or not, but asserting that any compiled language cannot be used to deliver software that has been implemented with Python, and that explicit support for OO is a relevant requirement, is something that flies in the face of reason.
With some very simple sharding (we are talking splitting lists and dictionaries) you can bypass the GIL and not balloon your memory usage. To do so you would use aiomultiprocess which inherits from asyncio classes (and therefore interfaces) but lets you await on methods running in their own processes.
Comments
Why?
I mean, come on. Who in their right mind would ever claim that Go is not a good choice to develop web services?
And are we supposed to turn a blind eye to Python's problems such as sub-par performance and the GIL?
I understand how Python fanboys will pick Python over alternatives whether that makes technical sense or not, but asserting that any compiled language cannot be used to deliver software that has been implemented with Python, and that explicit support for OO is a relevant requirement, is something that flies in the face of reason.
With some very simple sharding (we are talking splitting lists and dictionaries) you can bypass the GIL and not balloon your memory usage. To do so you would use aiomultiprocess which inherits from asyncio classes (and therefore interfaces) but lets you await on methods running in their own processes.
https://github.com/omnilib/aiomultiprocess