I'm glad the title of the article isn't some sensationalist junk like, 'App Engine should be shot in the face,' or 'Why I left the barren wasteland of useless A

I'm glad the title of the article isn't some sensationalist junk like, 'App Engine should be shot in the face,' or 'Why I left the barren wasteland of useless App Engine and moved onto the greener pastures of my homerolled Accumulo/Scalatra stack on Rackspace'. I think enough people who're reading this have had a good to fair experience with GAE and, like me, are wondering what hiccups other people are finding with apps on app engine. Subsequently, I also think that we like feeling smart because we've read enough docs and articles to be able to identify ways that their app's design may not mesh with the App Engine way of doing things. The thing I need to keep reminding myself is that there are many right ways to do it. If vpj and his cohorts are spending less time trying to figure out App Engine and more time on their app, then more power to them. At some point you have to just figure out when the effort expended outweighs the potential benefits and cut your losses, and I think this post is written in a clear and fair way. The thing that makes me upset though is that there isn't a central place that can clearly explains the pitfalls that he fell in, what the best way to do it on App Engine, and why. Those docs are kind of a mess, amirite?