Google I / O

On May 28–29, the Google I / O Developer Meeting was held in San Francisco.
The range of topics covered was quite wide: the Android mobile platform, Open Social, the brand new App Engine, all kinds of web-based client technologies (including AJAX) and much more; I’ll just describe a couple of points about App Engine.

For example, Offermann.us writes :

Use Django. Do not use the one that is included in App Engine (version 0.96). Yes, get the latest development version of Django 0.97 from the repository. And here's what is interesting: despite the fact that the webapp and Django 0.96 frameworks are supplied with the Google App Engine, Guido van Rossum devoted his speech to how to install and use Django 0.97 on the Google Application Engine. I was curious what webapp was for then, so I asked him a question: does it make sense to use it instead of Django. Guido replied that webapp is simple and allows you to launch something very quickly. But Django is more powerful.

Do not use count (). Never. (In Django, count () is a method that executes a SELECT COUNT (*) query on a database.) This has been emphasized in several presentations. Not only because he does not count more than a thousand , but also requires an analysis of each entity, which requires too much computing power.

And from there, an interesting quote:

In his presentation about how Datastore (the database interface provided by AppEngine) works from the inside, Ryan Barrett casually mentioned three significant priorities for the Google App Engine team in the near future:

1. Import and export data
2. Additional languages
3. Billing system

Unfortunately, the official Google I / O page is still outdated, and I could not find anywhere normal theses / presentations.