A lot of DataSci is academic adjacent. So DataSci tools are optimized for academics, not production.
-
-
I'm really hoping that the next few years of datasci can include an evolution towards better engineering support.
-
"Go read docs to figure out which library this routine is in" is fine for academic stuff but does not fly for engineering work.
-
Imagine if core file IO functions were spread across 5 different libraries. That's the status of datasci right now.
-
There is just no good reason for PCA to be in scikit-learn and SVD to be in numpy. They're the same damn thing modulo a symmetrization op.
-
I've wondered the same thing. Any hints of an effort to rationalize the ecosystem?
-
Seems to address only the numerical corner of the ecosystem, but otherwise cool.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.