Thank you very much. All right, here we go. Now it's time for really nerdy stuff. So yeah, this came about because I actually heard reporter saying to me after Docker became really, you know, all the hype cycle came up, people were saying, oh, we don't need the operating system anymore. And I've heard this time and time again. And as a former technology journalist, I can tell you that this is part of the normal hype cycle. And this is my attempt to say, whoa, hold on, ladies and gentlemen, that's not quite all the story. So here we go. A brief history of operating systems in the beginning. Hydrogen, helium, stars, dead stars, more stars, heavier elements. Silicon, iron, copper, you know the drill. They all come together. Some carbon gets together. It comes up that seemed like a good idea of life, you know, whatever. And then they got together. Let's take all those rocks, put them together, and make tools out of them. And one of those tools is the computer. Okay. But then they say, hey, we need to write some abstract math. They're sort of talked to these little pieces of silicon and metal to actually make them do something. And those would be the operating systems. And we have so many operating systems right now, it's not even funny. We have this, this has an operating system. That camera has an operating system. That has an operating system. That whatever that is on the wall. That has an operating system. The projector has an operating system. It's an operating system. They're everywhere. We live in a very operating centric, operating system centric world. Now we've improved on this a little bit. We've said to ourselves, okay, it used to be, you know, if you have a piece of metal, you're going to have an operating system on it. Unless it's a Windows machine and we're not going to call it OS because, well, no. That's, yeah, ladies, not a cheap shot. Number one. But virtualization helped us. We abstracted the operating system away from the metal. We could say, okay, instead of 1 OS per piece of hardware, we could actually have multiple OSs running. And that's what virtualization helped us do. But we still have the same problems. No matter where you go with these operating systems, you're still having to deal with the inherent problems that an operating system has, especially if you're a developer or a cis admin. These are still issues that have to be contended with. We still live in an OOS centric world. You know, we do well on some things on the planet, or we currently hold all the Mr. and Ms. Universe titles in the entire universe. I'm just saying. So we're doing really well there. But it's still been an operating system centric world and we're sort of now moving away from that. As soon as we did, people were like, oh, maybe operating systems are dead. Let's see. There are good reasons why operating systems sort of drive people crazy. We say, you know, developers, if you're a developer, you're writing your app. You're putting it on an operating system. Oh, the joy is of finding out that the latest security patch to that operating system just broke your app. You know, that you've worked so diligently to do. These are real, you know, this happens all the time. Admins have the same issues. They have to deal with the developers complaining about those security patches. Plus they have to get those security patches out. Because, you know, 500 people from some country across the planet are trying to get into that computer as we speak. Okay. And they have to deal with the inherent flaws. DevOps really doesn't do anything better. I mean, it makes the time to, you know, app development to deployment better. But still the underlying issue with dealing with operating systems is still a factor here. You can streamline the process. You can streamline it with DevOps deployments. You can streamline it with virtualization and cloud. But these are still going to have the same problems. The virtualization and cloud, they're the first steps. You can make things better. You can treat instead of treating operating systems like pets. You can treat them like cattle. Or if you're a vegan instead of treating them like heirloom tomatoes, you can treat them like a field of wheat. Okay. I just want to make sure we get that all in there. Okay. But now, now, and I mentioned this earlier, we have containers. Now containers are not new. They've been around for a while, be a state, call some jails, salaris, call some zones, Linux. They're built into the kernel. They're called, let it containers, LXC. But now they're getting a lot more height because of things like Docker. Containers, which are, if you're not familiar, they are basically file system and namespace containers of libraries and applications that run just what you need to run the application. They are very app-centric. If you write an app, put it inside a container, give it only what it needs to run. You can take that app, especially with Docker, pick it up, move it, and drop it on another Docker machine. You don't care what the operating system is doing underneath. As long as it's running Docker, you're fine because Docker will take care of everything else. That layer helps you make an app-centric world. So for that reason, containers are pretty much awesome. But not all the way. Containers are new. I mean, the old container technology is relatively mature. But the way we're using them now, we're trying to do things with containers that haven't been done before. So the technology is sort of growing and stretching. We see growing pains. Containers are leaky. We have containers sprawl where people just say, I'm going to containerize everything. And woohoo! And now you've got a million containers and nowhere to put them. So there are still some inherent issues there. So I've done a pretty good job now, slamming operating systems. And I've a fairly decent job talking up containers. So at this point, you might be asking yourself, why does anybody care about operating systems anymore? Now this guy, he may care about operating systems a little too much. It's okay to love your operating systems. But seriously, why do we care? Why do we need to have operating systems? Is this model really antiquitated? Are we really moving to something else? And I would say to you, no, we're not. And you'll probably be suspicious because it's like, hmm, he works for Red Hat. And overt is a virtual machine manager that deals with virtual machines that still depend on operating systems. Why should I listen to this guy? Well, because all of the developments that I told you about still were built on top of operating systems. So containers, and virtual machine managers, and hypervisors, and all the other innovations that we've seen since the dawn of the competing age. Since we figured out how to get a bunch of rocks and metal and silicon together and actually organize them to do really kind of cool things for us, like Twitter, that's cool. Okay, that's all coming from operating systems. This is the model that we've started with, and for now, this is the model that I believe that we will continue to progress with and innovate on. To give you an example of what, why I feel this way. Look at micro manufacturing or 3D printing. Oh my goodness, I've lost. Okay, 3D printing. I've totally lost this game. 3D printing, it's really cool. You can cut some, make anything you want. But it's not going to be the same. You can't 3D print cars. Yeah. Yeah, I suck. Every journey, yeah, that's okay. I'm going to beat all myself. So every journey that we make with operating systems, everything you do with an application, whether short or long, this is the Indian Mars Explorer that was recently got to Mars from India. You know, big achievement for that company. It all started from a small place like this small vocational high school in India. We all start from the same place, the same deep background. IT has to be innovated somewhere, and it's going to be on the operating system moving forward. They are the foundation, like it or not. Don't believe all the hype. Containers are great tools, but they're not going to be to be all in-doll for now. You're still going to need to work on operating systems and still innovate. So with that, am I overly long lightning talk, which is now a complete thunderstorm? Don't be a hater. Thank you.