I am uncertain about GAE given recent history, but have hope. Certainly given MS is deprecated, we cannot hold G. accountable for issues there. They **clearly** recommend HR, so MS app are 100% caveat emptor. However, the SO and Google Groups threads recently have been consumed with ire not limited to MS. A while ago, Jeff S. (whose posts I value the most along with Drake) posited that G. would have fixed the issues had they been able to do so. Going way back (when I started with GAE) billing was based on CPU milliseconds consumed. My guess is they thought this was highly disruptive. Then after beta, we got billed for 15 minute instance slices which was a big change from beta. This suggest that the initial assumptions were wrong (sh*t happens sometimes even if you are the brightest bulb in the pack). Overall, I think Jeff is right. There are some problems that can not be fixed given GAE's initial architecture. However, there may be some big changes coming with the App>Server architecture that only trusted devs (me excluded) get to enjoy. As I read the limited docs about what this entails, I wonder if this will be a fundamental change for GAE. It appears to fix most of my complaints, so I will be happy.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
