On Friday, November 23, 2012 11:45:56 PM UTC-8, Jeff Schnitzer wrote: > > Hmmm... I was planning to sit this discussion out, but some of this is > unfair. > > The support-related complaints are certainly legit. "Never have humans do > well what algorithms can do badly" is woven deep into the fabric of Google, > no surprise. > > The issue list is pretty reasonable. Stuff does get fixed, but it's a > long list. Please _don't_ close bugs as WontFix unless someone makes an > explicit decision not to fix something. It's unrealistic to expect a > roadmap three years out, which is probably how long it would take to fix > all the existing issues. >
Yeah, not buying that one either, really. However - and this is a big "but" - it drives me crazy how fast bugs get *introduced* in GAE and then not fixed for a long time. I'm still on 1.6.3 because that's the last release that didn't have a crippling (for me) bug. > The edges of GAE need to be treaded upon carefully. Avoid the email, > xmpp, and channel apis. Avoid backends. The bread-and-butter apis are > pretty effective though: datastore, task queue, memcache, and urlfetch. > Don't forget Objectify over JDO/JPA. I don't know why Objectify isn't the recommended API, other than I guess it's technically not Google's. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/xPlp7p0iBKgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
