 So, over to Peter, thank you. Hello everybody, great turnout tonight, nice to see you all here. Okay, and the wonderful word of the internet, and the internet of things specifically, we have at the board this little Spark funding. It's got Bluetooth, a 2.4 gigahertz radio, and it's based on an ARM processor. We also have things like the Arduino, the Nano, of course, STM32 board, another ARM computer, where we've done. This is the one that's got Wi-Fi and Bluetooth on board, so great for IoT projects. This one's got an ARM processor, Wi-Fi and Bluetooth. And what do we all have in common? Very little, this turns out. Some of them use ARM processors, some of them don't. So you end up using different IDEs with them, different source libraries, just about everything gets different. So when it comes to professional development, it's a little bit difficult. Then Google decided they would bring out Brillo, wonderful little project based on Android 7. Now, of course, it's got to the data stage, where they're putting more information upon the next. You can get their SDK reviews, your downloads, and start playing with what we have here. The Intel Edison, NXD Pico, Raspberry Pi, all of which my company's been kind enough to give to me. I like my voice. What makes these important and what makes Android things important is the fact that it's bringing standards. We're previously just very few standards. If we go back to the old days of computing, when we had the big 20, the Commodore 64, and so on and so forth, it was hard to write for anything because we were trying to support everything. So DOS came along and PC came along to start forcing standards on everybody. In my new, Android Things is going to do something similar for Android IoT. Right now, we have numerous protocols across the board for smart homes, for example. But Android Things uses the Weave protocol, which is basically brought about by agreements with Nest and other companies. So it brings some standards. It means that we now have one API to communicate between your smart controllers in your home, whether it's your air conditioning, your overloaded refrigerator with a super processor in it, or whatever it may be. These machines can now communicate with each other. We can put control around the world built by one company and have it interact with the air conditioning or ventilation systems, power curtains, or whatever it may be in your home built by somebody else. Android Things brings this to us in a nice, easy to use format where we have standard API supported by a large company. We also have standard operating system. Where the difference from conventional development is Android Things is obviously end-torted, embedded. So we're going to have to do a little bit more work to interface hardware devices. But not so much as we would have to do with the others. As if we take this Raspberry Pi 3. It comes with internet connection, USB ports and so on. Android supports the amount of the box now. Same with the other boards I have, the Intel Edison for example. It's looking at the Wi-Fi on board. Depending on the options you go with the expansion boards. You can also get internet. It's quite easy to use power over internet with these things as well as view adapters. And that becomes just a little bit easier for development. Yes, they cost more, but the costs are now coming down quite significantly on these high-performance computers. Which means for a lot of applications, it's just the Bible. Especially when you consider it reduces the cost of development. So that's why our company has decided to build their conditioners with Android Things in there. Now I had hoped to show you Android Things on this. But Google, you need to get things sorted, it keeps crashing. I've tried a few different cards, I've tried a few different images. But it'd be fair to Google, it is beta. So it's not something that's really ready for production yet. Of course, we should talk about some of the other differences. Traditionally, Android development is done with Java. Android Things has no Java. There's no Java virtual machine, so it's all sick-rolling. So that means us old-timers who, like our old traditional compiled languages, get another go. So, what else can I tell you about it? It's given me great hair. I've learned a lot of new things. I would like to give you a lot more gray hair, but there's a lot less gray hair to go gray. The joy is in getting all the day. So, any questions? Any questions, so Peter? No, no questions. So, just one question from me, because I mean, I use an Android phone. I'm a loyal Android fan. And of course, there's always this... I mean, I've got this old China phone, which is not the Xiaomi one. But basically, you know, I don't get the latest Android updates. I mean, I don't expect a Google to answer. But yeah, I'm curious, you know, whether with Android Things, you know, we have this side of fragmentation issues whereby you don't exactly... you run into issues with devices which don't exactly get the latest security updates. Any good thoughts on that? Yes. Choose the platforms that Intel directly supports. That's why we choose the... it's got a longer life expectancy. If you're going with something that's manufactured by third parties, then pretty much like the phone issue, you're satisfied with their support for it. Sometimes it makes sense to pay a little bit extra and go with a big voice. Okay, thank you very much, Peter. Thank you.