I don't understand the criticism on "shared environments" which the author latter voids himself, but what I do know is that Go makes a fairly good choice for extending Python, but isn't really in the same ballpark as Python.
Some thoughts:
- Go singlecore is actually slower than Python (nb Stackless[0] [still stands], but not only that: graalpython/loom is even faster, much faster)
- Prototyping is always slower in most AoT-compiled languages, obviously. I'd be more convinced to try Go if it had something like Cling[1].
- CSP is (in my opinion) less palatable than Actors and makes Go feel somewhat... dated? Matter of taste?
- Go doesn't use libc which can be awkward at times.
Some thoughts:
- Go singlecore is actually slower than Python (nb Stackless[0] [still stands], but not only that: graalpython/loom is even faster, much faster)
- Prototyping is always slower in most AoT-compiled languages, obviously. I'd be more convinced to try Go if it had something like Cling[1].
- CSP is (in my opinion) less palatable than Actors and makes Go feel somewhat... dated? Matter of taste?
- Go doesn't use libc which can be awkward at times.
[0] https://entitycrisis.blogspot.com/2009/11/go-vs-stackless.ht...
[1] https://root.cern/cling/