[cdong]

I don't get why a lot of people are calling mlflow a shitshow when it has done so much getting data scientist out of recording experiments via CSV. I can log models and parameters and use the UI to track different runs. After comparisons, I can use the registry to register different staging. If you have other model diagnostic charts you can log the artifact as well. I think mlflow v2 has auto logging included so why all the fuss?

[nerdponx]

People tend to forget that first movers rarely tend to also have the best design. MLFlow (and DVC) brought us out of the dark ages. Now we can build better tools, with the benefit of hindsight.

Claiming that something is "broken" or "trash" when you mean "I don't like it" is a good way to make yourself feel big and smart, but it's not actually constructive.

[cameronfraser]

There are those who create and those who complain on the internet about tools they've used one time

[isoprophlex]

Okay that's coming across as a pretty snide remark aimed at me, I'll bite.

Yes, I can understand why you comment that. I don't like blind slagging of free software either.

But there are ALSO those whose day job it is, and has been for the last 2 years, to use a badly designed overcomplex horrorshow of a tool that could be replaced easily by something better ... if it wasn't for the lock-in effects and strong marketing.

So I'm ventilating my frustration and at the same time expressing my gratitude to the person who made something fresh, that shows us things can be better.

I can't build the replacement to MLFlow myself, but I can cheer people on who do, and let them know their efforts are sorely needed.