[jimrandomh]

I have a hard time imagining who this wouldn't be a dealbreaker for. These terms also mean you can't use it for open source, and you can't use it if you don't know what the ultimate application is going to be. And you probably can't resell technology you create, because no one who buys it is going to want that restriction, either.

[zeroxfe]

It's not a dealbreaker for in-house ML applications particularly in the enterprise (banks, telcos, etc.), which is a huge market for cloud providers.

[fsloth]

Don't forget huge retail chains. Infinitesimal improvements in their operations can leverage, especially when compounded, sizable improvements to profit margins.

For instance, as GigaMart, if your ML system finds that you are going to need widget-x in region y two weeks ahead of time, you can plan for that including the logistics and inventory.

Hospitals? I'm sure there are lots of things in the day-to-day operations that correlate with patient outcomes that currently go unnoticed.

Etc etc. It's not about creating a huge new invention, mostly it's about creating improvements to operations of current incumbents.

[sodosopa]

That's how my company would apply the platform to our work. My boss is there now, will be interesting to see what he find out vs what we're doing with our current IBM platform.

[tixocloud]

Which industry are you in? Would love to get your thoughts on the IBM platform.

[sodosopa]

Health care. If you're running on-prem, it does a good job of integrating Kubernetes where it's not something my data scientists have to worry about. Also fairly easy to tie in our data mart and all of our databases - MS, Oracle, DB2, MongoDB, etc.

[bryanrasmussen]

But why would you choose this solution with those terms rather than something without those terms, even if it is an in-house application if significant investment is put towards it that is an asset that your enterprise now has and those terms are now in your enterprise poisoning it. Actually I can think of the large enterprises I've worked for and Legal would probably not have allowed those terms.

[devoply]

Whatever get your prototype going, get funding, build it on open source.

[deogeo]

No, because using it to get the prototype going is "using these Services to create (directly or indirectly)". Frankly, those terms look poisonous - you could be liable if any part of your service has origins in Google's platform. If you infringe on the GPL, you can remove the offending code. Here, you have no way to disentangle yourself from Google's trap.

[cloakandswagger]

I would imagine most prototypes would be made in a Jupyter notebook. I don't see any point in tying yourself to a platform intended for training/deploying models at scale if you're planning to switch off of it.

[throwawayjava]

...and then spend time and money building a company to near acquisition only to clutch defeat out of the jaws of victory.