>. I'm not sure they "sucker punched" anyone, I honestly believe that they sucker punched themselves as much as they did their developer community. There is not much that they could have learned over the past 3 years that they could not have anticipated from the very beginning. At the time when Amazon was charging back based on resources "hogged" (regardless if they are used or not) GOOG tried to outsmart everyone by charging for what is being used - without apparently (or so they NOW tells us) having any solution in place by which resources are indeed being shared and never hogged when not being shared. Even then, where I personally fault them the most is that they waited until they ran into (what at least seems) like a brick wall. Surely, they could have projected the inevitable after the first 3 months of real usage patterns analysis. So, Yes. In the process of sucker punching their developer community, they also sucker punched themselves because most of this fall out and damage is something that even their MONEY can not buy back and make right.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
