Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
1–10 of 27 posts
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#2It has some interesting model def features: The model interfaces abstract away where and how the model will be deployed so that the user can focus on what they understand best: the data going in and out of the model.
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#3Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#4Meanwhile, here is a list of open source ML deployment packages:
https://github.com/oracle/graphpipe
https://github.com/eliorc/denzel
https://github.com/tensorflow/serving
https://github.com/ucbrise/clipper
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#5Who cares about this garbage if the tool isn't even open source? There are lots of ML deployment tools that are open source. I know haters will downvote my post, but it's the truth. If I can't actually fork and evaluate a tool, it is hyped up garbage to me. Meanwhile, here is a list of open source ML deployment packages: https://github.com/oracle/graphpipe https://github.com/eliorc/denzel https://github.com/tensorflo…
Edited: Commenting about the voting, especially in the way you did here, is inappropriate too. We're here for substantive discussion.
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#6Who cares about this garbage if the tool isn't even open source? There are lots of ML deployment tools that are open source. I know haters will downvote my post, but it's the truth. If I can't actually fork and evaluate a tool, it is hyped up garbage to me. Meanwhile, here is a list of open source ML deployment packages: https://github.com/oracle/graphpipe https://github.com/eliorc/denzel https://github.com/tensorflo…
FWIW, the "Guidelines" ask you to please not dismiss work out of hand. Appearances matter, too - you can point out that a tool is proprietary and has lots of plausible FLOSS alternatives without being uncivil about it ("garbage"). Edited: Commenting about the voting, especially in the way you did here, is inappropriate too. We're here for substantive discussion.
But to be clear, I totally agree in terms of the degree and tone. I don’t think the parent comment you responded to was “uncivil” in any way, but overly dismissive instead of just noting to be skeptical.
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#7Earlier quoted context omitted.
FWIW, the "Guidelines" ask you to please not dismiss work out of hand. Appearances matter, too - you can point out that a tool is proprietary and has lots of plausible FLOSS alternatives without being uncivil about it ("garbage"). Edited: Commenting about the voting, especially in the way you did here, is inappropriate too. We're here for substantive discussion.
I agree with you, but I also think there’s room to point out that Uber has lost credibility and it wouldn’t be surprising or inconsistent if it was just a PR post for recruiting hype. Without details (not mere surface comments) on how it is differentiated from the many other available solutions and deep dives into what use cases it is specifically better suited for, it seems reasonable to treat it with a lot of skept…
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#8Pretty slick, but more impressive is their well written overview of the tool. It has some interesting model def features: The model interfaces abstract away where and how the model will be deployed so that the user can focus on what they understand best: the data going in and out of the model.
Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#9Re: Michelangelo PyML: Uber’s Platform for Rapid Python ML Model
#10Not too off topic: after mostly building and training models on remote compute (both at work and for my at home learning projects), I recently bought a fast laptop for home use that has a 1070 GPU and the experience of using a local device with a GPU makes me regret many years of SSHing to remote compute or using Jupyter remotely for machine learning development. I mention this as a lesson learned that may be helpful.