Geekly Articles each Day
📜 ⬆️ ⬇️

Excellent googled or impressions of Google Developer Day 2010


On Friday, the 12th, a significant event took place, such as Google Developers Day 2010 in Moscow. This is the penultimate event in the GDD series, the next will be in Prague on November 16, and the previous ones were held in Tokyo, Sao Paulo and Munich. GDD is a significant event for all developers and 4,000 people wanted to get there, as many applications were submitted. It was only 1500 and I was one of the lucky ones. About how GDD 2010 was for me, and I want to tell.

The conference was held in Crocus Expo, a giant exhibition complex, on one of the floors of which easily fit 1,500 people. From the metro, there were clear signs to everyone, which eventually led us to the 3rd floor to the reception desk with registration. Quickly passing it thanks to the registration codes sent in advance, we went to the pavilion, where everything was all to create a pleasant atmosphere: unobtrusive music, lots of soft seats, refrigerators with soft drinks, hot tea and coffee for those who just got up, games and entertainment - for those who came to get a fan, Wi-Fi - for those who want to surf the net. But everyone was waiting for the main thing - reports.
The conference was opened by Evgeny Sokolov, head of the Moscow development center, and Eric Tolome ( Erik Tholome ), director of products for developers. Eric, with his characteristic enthusiasm, told about all the updates to Google, which unfortunately was a spoiler for some of the reports and spoiled the impression from them. In order not to repeat this experience, briefly go over the key points of his speech.
What is new to us HTML5:


What is new to us App Engine :


Then we started talking about GWT and development such as Spring Roo . Spring Roo (SR) is an analogue of Django, but only on java. SR takes over the backend, and GWT takes over the front end. Before our eyes, Fred Sauer, to whom Erik passed the word, showed how from the command line you can create a simple application with a certain set of entities, configure them with Hibernate and generate a UI for GWT. Then Fred launched Eclipse, for which there is a special plugin Google Plugin for Eclipse and launched the application in front of the public. (By the way, a single word about the demos - almost all were demonstrated in FireFox with poppies.) The demo worked with a bang. Fred also showed another SR chip - redeployed, after changing the essence. Separate customization options - configuration for deployment to Google App Engine.

Thanking Fred, Eric almost immediately gave up the microphone to Reto Meier, who spoke in some detail about the prospects of Android development. According to his words, today released 90 types of devices running on the Android platform. Without becoming delved into the technical details, Reto spoke about the possibilities that the Android Store provides, namely:

')
At this conference was declared open and earned 5 sections:


In each section, there were 6 reports each (this is if monetization and the social web were merged into one), so a total of 24 reports were read, and at times it was terribly like to break. But in the end it turned out what happened. Let's go in order.

How to write epic applications for Android
Reto Meier ( Reto Meier )



Reto built his report in 4 positions:


Here is what I managed to extract for myself. First, you need to work a lot on performance and use, for example, Threads / AsyncThreads. At the same time, it is imperative to keep the user fully aware of what is happening in the application.

Of course, the application should be user friendly, so do not forget about user experience:


With regards to programming style:


One of the most seemingly obvious tips would be to call in a designer. For all its obviousness, it is often forgotten.

Reto finished with a story about how important it is to integrate an application with analytics to get the following data:


What's new in App Engine

Fred Sauer

Channel API

This API is intended for direct communication between the server and the browser client.

What is there now:



MapReduce

MapReduce is a framework for computing some sets of distributed tasks using a large number of computers forming a cluster. In the course of the story about MapReduce, Fred regularly spoke “magic!”. Part of MapReduce is the Map, for which the Mapper API is open. A few words about him:



Namespace API

This API changes the usual work with datastore and memcached storage, adding the namespace field between the key and the value. One of the obvious applications is working with different versions of the program.

Matcher API

An interesting system, which so far, sort of like. implemented only for pythone. Allows an entity to match fields to any values ​​according to the condition we have chosen. Applicable for migrations and reporting.

Hosted sql

This functionality allows you to store on the server a set of SQL queries that can be launched by pressing 1 button. Which is convenient for generating demo data and also receiving reports.

Admin console

Comfortable admin to work with most of the functions sounded above.

Saturated spiritually, we began to be saturated financially - lunch began. Everything was organized very well, since there were no special rush and queues. The food was delicious and it was enough. Also very pleased with free drinks in refrigerators.



Having a little rest, we again rushed to find out and enjoy the new.

Practical HTML5

Jeremy Orlov (Jeremy Orlow)

Jeremy first talked about the changes in semantics, namely:


Next, we moved to canvas:




Then there was a demo and a story about:


Well, finally we switched to css3:


Together with Jeremy, Vadim Makeev , also known as pepelsbey, gave a presentation on “Special Effects Tea” .

Data processing at high loads in App Engine

Mike Aizatsky ( Mike Aizatsky )

By the way, it was the most eventful of all the reports. It began with a description of the problems faced by App Engine users:


Then Mike brought out several concepts that change the familiar look at the LAMP approach:


And to solve these problems, two approaches are possible: low-level and high-level.


Low-level technology

Named tasks:


Hitch tasks:


Transactional Tasks:


Record groups:


Named Records:


Synthetic properties:


High-level technology

Here Mike suggested the following:


I hope to find this presentation, as I was not able to record anything. After that, it was absolutely necessary to have a rest, so the break came in handy.



Web apps in the Chrome WebStore

Paul Kinlan

Paul started with a story about what should be in good modern applications:



After that, Paul turned to enumeration, why was Chrome WebStore created:



And I completed the entire report, which I waited with great impatience.

Mobile development: HTML5 or Native?
Reto Meier, Mike Schemof (Reto Meier, Michael Mahemoff )

For a start, the speakers determined when it was worth writing this or that application.

The power of native applications:





The power of html5 applications:

Here, by the way, Michael brought an interesting slide of the form:
Processing speed js code:

DOM processing speed:

Excellent comparison, I think =)
In addition, web technologies allow us to work with geolocation and many other things, access to which is provided by hardware.
As a summary of the report, the following thought was put forward that the ideal is a combination of Native and HTML5 applications, which allows for example PhoneGap and Titanium .
At this GDD was almost over, there was only the final word and a buffet that summarized this wonderful and busy day.

As a postscript:

Source: https://habr.com/ru/post/108137/

More articles:


All Articles