When I first looked at GAE a year ago, it really looked like Python was the preferred / "native" API, I seem to recall there being features that were some features available in Python but "not yet in the Java API", and in fact that was major part of the appeal.
A non-standard proprietary database and API was not ideal, and as a longtime Perl hacker I wasn't overly keen on python, but GAE seemed to offer some useful value-add features over a plain LAMP stack, and at least I wasn't being forced into some "enterprise framework" (/shudder/ - I've seen the mess these things are used to build). If it turns out that python was more of a stopgap, and GAE is starting to quack like a yet-another-java-framework, then I'll simply reverse my port back to a LAMP stack or similar. It'll be with some regret, but there you go. I know Google have been building a lot of internal systems on GAE (and Ben Fried is a very smart bloke), but it does make me wonder if this has skewed their view of the product over time - it's quite a common danger with dogfooding your own product (you end up building the specific product you want, not necessarily the one the clients want). -- 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.
