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. 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. Yes, they do sometimes get slow - and you need to understand that the task queue and cron are best-effort, and design appropriately. This behavior is well-documented, although many people seem to ignore it. >From what I can tell, Brendan has a particularly exotic architecture that involves decomposing his application into lots of appids and relying heavily on backends. There has been banter on this list before about whether this is a good or bad idea. One thing for certain is that this is not mainstream app design on GAE... so when you hit snags you may be out there alone. Jeff On Fri, Nov 23, 2012 at 11:18 PM, hyperflame <[email protected]> wrote: > > On Friday, November 23, 2012 4:40:07 PM UTC-6, Kristopher Giesing wrote: >> >> I haven't heard a credible refutation of anything Brandon wrote in the >> original post. My own (admittedly limited) experience is very consistent >> with Brandon's description. > > > +1, to you and to Brandon's list. > > I'll add to Brandon's list: the bug tracker. There are issues there that > have been outstanding for literally years, and there is no clear roadmap of > when issues will be fixed. Quick examples (that I'm picking because I'd > really like to see them fixed): > > Issue 2314 ( > http://code.google.com/p/googleappengine/issues/detail?id=2314 ): Making > inbound email work for custom domains. This shouldn't be too hard, custom > domains already get hosted Gmail, why can't App Engine access the inbound > mail services of Gmail? Yet this issue was filed in 2009 and acknowledged > by Google engineers in 2010. It's almost 2013, and no followup. I'd like > some details on this; will this be fixed soon, or do I need to buy a > subscription to context.io/other external mail services and use their > incoming mail parsing services? > > Issue 2145 ( > http://code.google.com/p/googleappengine/issues/detail?id=2145 ): Same > idea, make custom domains work via the XMPP service. Filed in 2009, > acknowledged in 2010. No roadmap for implementation. This is pretty much > required for using XMPP professionally; Jabber IDs with @appspot.comsimply > don't look professional. > > Issue 739 ( http://code.google.com/p/googleappengine/issues/detail?id=739): > URLFetch operations don't follow no-caching headers. This issue has been > marked Fixed, but I still get cached and stale urlfetches even after > setting cache control headers, setUseCaches(), etc. I'm not the only one > having problems, just check the issue. > > Issue 1741 ( > http://code.google.com/p/googleappengine/issues/detail?id=1741 ): The > ability to remove a named task from a queue. Filed in 2009, accepted in > 2010, absolutely no feedback since then. More fine grained control over > task queues in general would be nice. > > > Leaving issues open for years is insane, give us a roadmap to when you'll > fix these, or close them as Won'tFix. > > -- > 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/-/SCXgXmZivIMJ. > > 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. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
