For me, the allure is writing performant functions in a safe language. Further Go's scientific computing story is evolving quickly, and grumpy lets you call into Go without even writing bindings (though they would probably be convenient for marshaling between Python and Go types). Still, grumpy has a long road ahead, and it's probably slower even than CPython for sequential execution.
No matter how quickly Go's scientific stack evolves it's still going to be well behind Python's stack which is also evolving rapidly and has been for 20+ years in physics, climate science, GIS, etc - and most of that is built on CPython C-extensions. (And as a bonus issue, many large projects are committed to dropping python2 support within the next couple of years).
I was about to get really excited about this and then noticed that it only supports Python 2.7. :[
alcalde 6 points · Jan 2017
Between that and losing the ability to use libraries like numpy, it's only going to be interesting for a segment of Python users.
weberc2 3 points · Jan 2017
For me, the allure is writing performant functions in a safe language. Further Go's scientific computing story is evolving quickly, and grumpy lets you call into Go without even writing bindings (though they would probably be convenient for marshaling between Python and Go types). Still, grumpy has a long road ahead, and it's probably slower even than CPython for sequential execution.
mangecoeur 3 points · Jan 2017
No matter how quickly Go's scientific stack evolves it's still going to be well behind Python's stack which is also evolving rapidly and has been for 20+ years in physics, climate science, GIS, etc - and most of that is built on CPython C-extensions. (And as a bonus issue, many large projects are committed to dropping python2 support within the next couple of years).
weberc2 1 points · Jan 2017
I mean, that's what everyone said about its web story. Maybe you're right, this isn't my domain.
Flogge 1 points · Jan 2017
Why would sequential execution be slower?
weberc2 1 points · Jan 2017
Lock contention, presumably.