 Thank you very much, so I actually managed to come with a hundred and seventy-four slides. No, I'm sorry, it's really many fewer slides than that. I'm going to take a bit of a different angle, but I'm actually going to focus on a very salient part of what Simon spoke about, which was your data and how that applies to the change from regular computing where you own your data and it's on your own machine and it's available to you at any time to where it's available through cloud service. But I'm also going to talk a little bit about openness and why how this all sort of relates together. So there's a number of reasons that we think openness matters. I started at Google on the open source team, I'm still on the open source team, I've moved on open data matters as well. But fundamentally we believe that open technologies, open data, open web is a much more useful system for consumers. The canonical example here is the car. Your car is much more valuable to you if you can open up the hood and put more fluid into it, change the oil, that sort of thing. If you would have purchased a car with the hood welded shut, it becomes certainly much less valuable to you. So the open web should be, for everyone, is the view that we take. Innovation, idea sharing, opening your technology so that others can use it is changing the web of ten years ago to what the web is today and where it's going in the future. So this is a web where everyone can innovate, most importantly without having to ask permission or negotiate deals or contracts or that sort of thing. This speeds it up a great deal. Beyond that, the accessibility to the web should be through standards-based clients such as web browsers, open source web browsers like Firefox, Apple's WebKit, Chrome. These are all very important players in this game. The fact that we have an open network where you don't have to negotiate deals or payments to join in, it vastly lowers the barrier of entry for people, webmasters, engineers, developers, companies. And it reduces inefficiency and you see a lot of that sort of transition that Simon was talking about in his slide from innovation to spoke up to commoditization. Now, we'll set the way back machine to the mid-90s when the web was very nascent. People were starting to develop applications, services of the web. People spend most of their time writing basic infrastructure, plumbing. Everybody did it. Everybody did the same thing that everyone else did just in different fashions. Now, the equivalent of that in a very tangible metaphor would be one of construction. You have to forgive my construction metaphors. I'm working in my house right now, back in the States. Imagine if you wanted to build a house. So what you typically would do is if you're capable of building your own houses, you'll purchase bricks, you'll purchase lumber, nails, and the other bits. Required, you would find someone capable of assembling those into something that vaguely resembles a house. 12 years ago on the web, the place that we were was basically where you would have to buy cement, sand, raw iron, forge into nails, and then start planting trees that you could grow your own lumber for the house. Clearly, this is an inefficient way of building your own infrastructure. 90% of people's time was spent focusing on building the things that they needed to build what they wanted to build until like 10% of their time was actually solving their problem, focused on what they needed to do for their users. Now, an example of where we are today that is sort of allowing this to change this is, if you wanted to do, say, a map of all the restaurants in Brussels, the first thing you need to do is get in your car and get a bunch of paper and go and map the whole city. Then, once you map the whole city, you digitize it, you put it up on a website, and you start adding your restaurants to it. Again, you spend 90% of your time building your basic plumbing and infrastructure. If you were to use an online map system, the example we have would be Google Maps, and in this case you could take your list of restaurants, your addresses, inject them into the maps, and since all the mapping infrastructure is done for you, you can focus your time on maybe doing restaurant reviews, finding the best place for wine, the best restaurant for steak, pasta, etc. What this common infrastructure does is it allows people to start trying to solve a problem, to focus more on the problem and focus more on the user experience as opposed to things that really aren't relevant to the product at hand. Two slides. Again, we think that openness is an integral part of the web and continuing innovation on it. We don't think that we could have gotten to be a successful company without this openness. Larry and Sergey, back in their dorm, did negotiate a deal or a contract to set up a new search engine on the internet. They nearly acquired a computer and plugged it in, set up an address, and off they went. But this open innovation is important, it's important that we continue this so that other startups, other innovative companies, disruptive technologies, can come to the fore and provide better services and experience for consumers. So I'll briefly touch on a few ways that we sort of contributed back to the open web. Some of these are through services. We've created a Google Code, which is a site similar to SourceForge, where open source developers in particular can collaborate and host their software.