3 ms·
yeah, and we should all be happy when we are forced to migrate to new APIs...like the old APIs got rust. This's one of the reasons why proprietary "cloud" servi
by themihai 9y ago
yeah, and we should all be happy when we are forced to migrate to new APIs...like the old APIs got rust. This's one of the reasons why proprietary "cloud" services are so bad. Once they are gone you have little or no choice. Nobody would complain much if Google would shut down its MySQL "cloud" service. Amazon is just there and if Amazon doesn't fit the bill you can use a old good metal server. Not the same you can say about Google Cloud Datastore, Appengine or this ML API
- skybrian 9y agoTensorflow is open source and apparently very popular, so I'm guessing this migration would be moving in the direction of less lock-in.
- neurotech1 9y agoWhen will Google open source the Tensor Processing Unit, or something similar for FPGA accelerated TensorFlow?
- themihai 9y agoMy point is that the business owner/developer should decide when to migrate to a different API or if it even makes sense for them to even migrate, not Google. The lock in was a bad idea in the first place. I may exaggerate but what's the point to have a new/better solution(Tesorflow) if the migration kills your business?