Re:Google opens access to its speech recognition API
by mianos on Wednesday March 23, 2016 @05:23PM
(#11348374)
It is funny reading this in hindsight. We went straight to AWS, also for long running tcp connections, and never looked at it again. After that I have never recommended app engine.
Re:Google opens access to its speech recognition API
by bduerst on Wednesday March 23, 2016 @06:28PM
(#11348768)
Wasn't that five years ago? When it came out of preview (and prices were expected to change)?
Re:Google opens access to its speech recognition API
by sologoub on Wednesday March 23, 2016 @06:35PM
(#11348815)
It was - 2011 is mentioned in both article and my comment.
I just wish Google wouldn't bring back memories of that by not disclosing pricing of a very promising API.
GAE has moved quite far ahead since then, but many people still won't consider it after the bad experience. Perceptions die hard...
Re:Google opens access to its speech recognition API
by dragonwriter on Thursday March 24, 2016 @03:11AM
(#11351109)
They probably are using usage data in the free period to drive decisions on pricing.
Re:Google opens access to its speech recognition API
by sologoub on Thursday March 24, 2016 @02:44PM
(#11355263)
Sure, would expect nothing less, but I'm also sure they have some sense of the range they are looking for. Such a range could help developers to establish whether their use case is viable or not.
As is, the ambiguity is a deterrent from too much time investment.
AppEngine pricing change resulted in a nasty surprise for a lot of people and a lot of vitriol towards Google. Just one article on this from many: http://readwrite.com/2011/09/02/google-app-engine-pricing-an...
While the platform has moved way ahead of where it was in 2011, the memory of this is still in the back of people's mind and it would be a good move on Google's part to at least try to engender more trust by giving directional pricing.