Is Einstein Analytics shifting from hybrid C-Python towards Google's Go language ?

According to Salesforce principal architect Guillaume Le Stum, before Salesforce launched Einstein Analytics, the query engine and dataset creation tools that eventually became Einstein Analytics were written in C "for performance" and a Python wrapper that provided functionality like parsing queries, and a REST API server. 
But before launch, Le Stum says the guts of Einstein Analytics started to show performance slowdowns because any new feature that wasn't part of the core query engine got loaded onto the Python wrapper and shifted to the Go application. 
Is the Le Stum claim of "Python doesn't do multi-threading very well, so the more the wrapper was being asked to do, the worse it performed," is acceptable. 

No comments: