That's mentioned in the article, but is the lock-in really that big? In some cases, it's as easy as changing the backend of your high-level ML library.

▲

LogicFailsMe 6 hours ago | parent | next [-]

That's what it is on paper. But in practice you trade one set of hardware idiosyncrasies for another and unless you have the right people to deal with that, it's a hassle.

▲

lvl155 6 hours ago | parent [-]

On top, when you get locked into Google Cloud, you’re effectively at the mercy of their engineers to optimize and troubleshoot. Do you think Google will help their potential competitors before they help themselves? Highly unlikely considering their actions in the past decade plus.

	▲	LogicFailsMe 3 hours ago \| parent [-]
		Given my Fitbit's inability to play nice with my pixel phone, I have zero faith in Google engineers. What else would one expect when their core value is hiring generalists over specialists* and their lousy retention record? *Pay no attention to the specialists they acquihire and pay top dollar... And even they don't stick around.

▲

tempest_ 5 hours ago | parent | prev | next [-]

That is like how every ORM promises you can just swap out the storage layer.

In practice it doesnt quite work out that way.

▲

Irishsteve 6 hours ago | parent | prev [-]

I thin k you can only run on google cloud not aws bare metal azure etc