Google App Engine Frustrations
- Posted by admin on July 20th, 2008 filed in Uncategorized, general, python, web technologies
I've tried more than once to jump onto the Google App Engine bandwagon to no avail. Unfortunately it's preview nature is acting to frustrate any attempt I make build something I'm happy with. Just some thoughts so far:
No Direction - It's been dumped into the ether with no solid direction. No recommended method or path to building your web app is given or hinted at. I'm all for choice and its great Google allow you to use Django, CherryPy, WebPy, etc. but it'd be helpful if a consistent and solid method was given. Unfortunately you're left with the feeling that the GAE has been thrown together with no real thought of making a web app out of it.
Disorganised Documentation - This doesn't help the problem mentioned above as the docs provide 3 or 4 ways of producing a web app from the start. It first tells you how to do it using basic CGI and printing directly to the browser. Then it shows you using the RequestHandler and WSGI app. At which point it doesn't say URLs are now handled by the WSGIApp instead of the app.yaml. Then it brings Django templates into the mix. How about pretty URLs? Oh well we can do that in app.yaml, or using matched groups in the WSGI app. For the love of all thats holy can't we just have a single nice solution? A recommended method? An idea? A guide?
Restrictions - So it gives you all that wonderful choice as mentioned above so you think you're going to make the best of it but oh no. Now you have to put up with the restrictions. No MySQL, no Django admin, restricted URL retrival, restricted security, no file uploading.
So you have to ask the question: Why?
What, ultimately, is the point in it when there's far better out there - Django, Merb, etc. It has no purpose other than to faff with and so I shall be avoiding it for the forseeable.
Related
Leave a Comment