>> Announcer: From around the globe, it's theCUBE. With digital coverage of Dockercon live 2020. Brought to you by, Docker, and its ecosystem partners. >> Hey, welcome back everyone to the DockerCon 2020, #DockerCon20. This is The Cube virtual coverage with Docker on their event here. And we're in the studio in Palo Alto, I'm John Furrier your host of theCUBE, we're here with a great guest to talk about Docker Desktop, the Microsoft relationship, and the key news that's coming out. Ben De St Paer-Gotch is the product manager for Docker Desktop. Ben, great for coming on, thanks for spending the time with me. >> Thanks for having me, I really appreciate it. >> So obviously, this is a virtual conference, we wish we could be in person, but given the state of affairs we're going to do remotely, but the momentum Docker has is phenomenal, it's always been great with containers. It's the number one downloaded app around for developers. Microsoft just had their Build conference, which was again virtual as well, or digital, as they say, it's interchangeable. But clear momentum now with Docker as containers actually is the standard, you guys are doing great. What's the key news out of the Microsoft world for people who missed it last week with MS Build? >> Yeah, so last year at Build, Microsoft announced WSO2 to the Windows subsystem with Linux two. (mumbles) The mapping between the windows (mumbles) Which, went really well but it just didn't provide the same centered needed Linux experience. Last year, they announced Windows subsystem Linux two, (Provides an actual Linux one on windows machine, and we've been working hard with Microsoft over the last year to integrate proper desktop as a main desktop application for working with containers with WSO2. A build this year, Microsoft has gone on and announced that WSO2 is going to have a few new features, and it's going to have new features. (mumbles) Mention Linux graphical, Linux applications, you can access the file system, the installation is going to become a slicker which I guess I'm the most excited about that pitch. But the most exciting announcement is, they will be bringing GPU support to WSO2 which means that we will be able to provide and give you support through Docker desktop or container workloads that peoples are working on. And now we're launching Gray and Agua through containers and docks and desktops and Windows which is really cool because we haven't been able to do that before. >> So is this the first GPU support on Microsoft Windows for Docker, with Docker? >> It's, yeah, it's the first GPU Support for Docker Desktop or Mac or Windows. So, previously the hypervisor hasn't passed through the GPU, pretty much, which meant that we couldn't access it from Docker desktop. So Docker desktop isn't about a lightweight VM we sorts of plumb all that in for you. But we're limited about what we could get access to from the hypervisor, Microsoft putting this through and giving us access for the first time, we can actually, we can go. >> Not to go on a side tangent here, but you know, all these virtual events, and I was watching some of the build stuff as well, as well as us immediate streamers and doing stuff, you can see people's home rigs. And you talk to any Developer, video streamer, or anyone who is working remotely, if you don't have the best GPU's in there, I mean, this has just become, I mean, quite frankly, you need the GPU's. So this is important, it's not only from a vanity standpoint performance. Having that support, I'm going to want the best GPU's, I'm always going to be upgrading my machine for that extra power. What's the impact? What does it mean for me as a Developer? Does it increase stuff? What's the bottom line? >> As a Developer, it means you actually have access to it. So, especially when you're doing workloads on the CPU, you've got minimum amounts of power utilization you can do. When you're running workloads for an L Development, you have a lot of power up process you've got to log, to do your mobile training. So, in an element cycle, you're likely to have your application which you're going to use to produce a modeling, you're going to have training data. Taking that training data and producing a model requires lots of panel processing which is an enormous calculations in producing with finer waitings. Doing that on a CPU has to be done on a serial fashion rather than parallel, which is huge and intensive and takes a really long time. Whereas on a GPU, you can do all of that in parallel which massively reduces the amount of time it will take to run those training functions. Either just straight up in Linux or running them in a container, which as the more of people are looking at running container with workloads, it's how I first, the first team that I was on actually used Docker. I was working in Amazon Alexa, and my team picked up the opportunity to run our workload in container. And that was my first experience, so even though my team backed down, so I could see the system. >> Yeah, ML workloads automations could be critical of that performance. Okay, let's get into some of the momentum with Microsoft, you guys have obviously, builds over, we're here now at DockerCon, there's news. Could you share some of the tidbits for what's being talked about now with Docker and DockerCon. >> Yeah, absolutely, so, along with everything else we've been doing, we've been partnering with Microsoft trying to make the best experience generally with Docker desktop, and with WSO2 and with the VSCO. I've been working closely with Microsoft guys to actually try and improve our experience in Windows as it is today, and to improve some of those integrations with VSCO, and also working with the VSCO team on the Docker plugin for VSCO to give our feedback, and to hear feedback from those guys on the errors and issues they're seeing with Docker desktop and to really try to produce the best experience we can on Windows. End to end, from very front end running all the way through that first push, that first run on the cloud using Docker. >> So what is some of the new product management processes and customer support things that you guys are doing? This comes up a lot, obviously, we had a great conversation around shift left with security. That's great news there. You start to see a lot of this added value for Developers, wanted their support right? So how do I get things I need, and from a customer standpoint? It's kind of a moving train this world and it's only getting better and better from a Developer standpoint. But there's more complexity, it's got to be abstract the way you've got, you know, this new abstraction layers developing. You've got a lot of automation. How does the customer get the support they need in the same agile way that Developers are cranking out code? >> It's a really good question, it's something I think we're still working on as well. So, we're trying to working out and one of the big things I'm trying to work out is, how to make it easier for people to get started with Docker, and how do we also make sure with the things we build, we don't leave a cliff edge instead of a lining path. You don't get to a certain point in an easy process, and then the next step, takes you straight off a cliff, so that's not useful for anyone. So, producing those parts and those ways for people to learn and actually progress is something we're really trying to work out. How to make it natural from the first experience all the way through. From an actual support perspective, the other thing we're looking at, is we're trying to do more things in the open. We're really trying at Docker to bring as many of the new features and pieces we're developing which we have to do that in the open with community visibility, so that if people really want it fixed, they can open the PR and they can help us out. And then the last thing that my team really stood out was our Docker of having actions. As creators, someone already finished, could you do this? Someone else had a PR and emerged it. So, to a certain extent, you've got your one side which had you on board and this ever growth spiral and you keep learning. The other side is how'd you fix the board when you find an issue? In that one, we're really trying to work with the community, a lot more than we have in the last couple of years. >> Awesome, some folks watching, hit him up on Twitter, he's the Product Manager for Docker Desktop among other things. You guys are very transparent, you've got your Twitter handle on the lower third. People can chime in or just jump on the chat, we'll follow up and get you the info. Final question for you Ben, as you look at this reality we're in, there's kind of a holistic kind of moment now where people kind of realizing the new realities here. You're looking at the.. you get the keys to the kingdom with Docker Desktop, okay. You got some momentum with Microsoft, the developer role is moving fast and fast as the head room increases for capabilities with automation. And I know you mentioned a few of those things. GPU is now available. What's the future look like for these Developers? The next short, medium and long term? What's your view as you look out over the landscape because you've got to look at the product roadmap, your engagement with the community. Can you share some insight into how you're thinking about Docker Desktop going forward? >> Yeah, absolutely. So, I think what really interesting point as you say, which is that, if you look at sort of a lot of the Developer side of things that have sort of come out in the last like six months, six to eighteen months. The things I see, I see daily like you mention, things like orchestrating for containers gaining momentum. If you think about crossing the Kaizen model, we're just passed the early Dockers now. We're kind of into the early majority, but we're going to start to move over the next few years into the late majority. What that really means is that people here have been using one of two of these technologies. Maybe you've been using cloud, maybe you've been using Edge, maybe you've been using containers, maybe you've been using CICD, maybe you are using Expiration, maybe you're not. Maybe you've got a Microservice application, maybe it's a little bit of a mole rat. What we're really going to see is, you're going to start to see, all of these changes intersecting and overlapping. And people who have started to pick up model two of these will start to pick up all of them. And that's probably going to happen as we move into the majority of users. So from a what's coming instead of a lot of those thing that you see in best practice in the ideal Developer setup, so a beautiful CICD, a more of an orchestrated environment, Microservice architecture, we're going to see a lot more of that becoming the norm. But I think along with that, we'll also see a level of recognition coming along that a single Microservice alone doesn't provide value. And that's it's going to be some of those groups of services that will provide the user outcome. And that's where my focus is at the end which is you know, an authentication service is great but it doesn't provide value unless you give access to something as authentic. >> It's been issued that the new Docker is all about Developer experience. This is really the core mission. I mean, since the sale of the piece of morantis, Docker has retrenched and reinvented, but stayed core to its principles. Just share with the Developers who've been watching that are coming back into the ecosystem, what is this new Docker vibe? Share your thoughts. >> The new Docker vibe is about working in the open, and it's about solving problems for Developments. The original goal of Docker was to make it easy to pack and ship. It was to reduce Developer friction. As we move more into, sort of, the enterprise space, we worry more about Ops and DevOps. We're not trying to re-focus on Developer and if you sort of think there's two parts to the Developer life cycle, where you've got your work, where you're doing your creative work, where you're writing code. And then you've sort of got your part of the inner loop. And then you've got your part where you're trying to get that code out to production, you're trying to get your value to someone else. Instead of your outer loop, we're really trying to focus on the inner loop And sort of our mantra is that any bit for a Developer should spend as much as their time as possible creating new and exciting things and we're onto those holes that reduce those boring, Monday, repetitive tasks, that we're really trying to work out how we take those boring repetitive pieces and how do we make them just vanish like magic from new users or how do we reduce the friction for the experience from users? From both desktop and hub, we're really trying to bring those two together to achieve that. >> You know what's great about folks who have been in the class since day one. All of us have scar tissue experiences, you know the one thing that's constant is constant change. And one of the things that you guys have done at Docker, and hats off to the whole, you know, original team, is that brand of Docker has symbolized quality openness, and set the standard, I mean, if you look back and containers were really coming around, it's not a new concept. But Docker really set the industry on this path and it's been great to follow every DockerCon at TheCube coverage, but more importantly, as the demand for Developers to build these next wave of Cambrian explosion of applications. It's going to be more important than ever to have more of these abstractions, more of these tools in this real time, more Developers experience because there's more building going on. And it's not just one cloud, it's all clouds, it's all things. >> Yeah, I think it was like when IDC analyzed the future report a couple years ago, I think it was maybe the 2018 one. They said that maybe 2017. They said to date, we've built 500 millions applications worldwide and by 2023, we'll build another 500 million. The rate of creation is just insane, it's exponential growth of us producing more and more applications and connecting more and more devices to do them. The sheer volume of creation and the rate of new technology supporting, even with the rate of companies adopting, I guess more of a warm cloud. I think it's like 60 percent of companies are now more than one cloud provider. Maybe even more, maybe it's like 80 percent. It's ridiculous. >> I was just having this debate on Twitter about this multi-cloud. Someone tried to call us out saying, "Oh you guys were pooing on multi-cloud in 2016 and 18." I go "Look at, no one was Pooping on multi-cloud, it didn't exist." I had multiple clouds but there was no real use case. Now you're starting to see the use cases, where yeah, I had multiple clouds and I got Azure here, I got this over here. But no one wakes up and spreads their workloads wrong. This is going back a few years. Certainly the hybrid was developing, but I think now you're starting to see with networking and some of these inter-operable dynamics, you start to see innovation pockets in wide spaces in large market opportunities for start-ups and companies to thread the clouds together at the right place. So I think multi-cloud is becoming apparent from a use case stand point. Still a ton of work to do, I mean direct connects, got SLA's, I mean all kinds of stuff at the networking level but it is real. It's going to be one of those realities that everyone has, at least one or two, if not three. It could be optimization, this is what Developers do right? Solve problems. >> Yeah, absolutely, I mean if nothing else, I've encounter a couple of companies even just where redundancy is handled by multi-cloud strategy. If you want to achieve more nines and you're just balancing workloads between two clouds. >> I mean, the Zoom news was really a testament to that because everyone got into a twist over that. Oh Zoom moves off Amazon, no they didn't move off Amazon, they went to Oracle, they got Adge, they're everywhere. Why wouldn't they be? They need to pass it, they fail over, they need fall tolerance, I mean, these are basic distributing computing concepts that is one on one. You've got to have these co-locations. And optimization for those clouds and the apps on Microsoft as well, so why wouldn't you do it? >> Exactly. And that's that hybrid, that multi-cloud, compounding that some of which you said earlier, that over changes when you're looking at how you go to CICD, how you're bundling these applications, creating more applications than ever. Coming back, sort of, with more AI workloads, much like GPU and you combine that with, sort of, last in the growth of age devices as well. It sort of makes for a really interesting future. And Docker is sort of, that summation SOV, what we're using to frame how we're thinking about our product and what we should be building. >> Great, for the audience out there, hit him up on Twitter, Ben's available, they're out in the open, if you're interested in how Docker makes life easier on the Windows platform, with the GPU support, they've got security now built in, shifting left. Give these guys a call and of course, we love the mission, out in the open. It's theCUBE's mission as well and great to chat with you. Ben, thanks for spending the time with me today. >> Been an absolute pleasure, thank you for having me. >> Okay, just TheCube's coverage, the virtual Cube with DockerCon co-creating together out in the open. DockerCon20, #Docker20, I'm John Fer with TheCube, stay tuned for our next segment, and thanks for watching. (ambient music)

>> Announcer: Live from Orlando, Florida, it's theCUBE, covering Microsoft Ignite, brought to you by Cohesity. >> Good morning, everyone, and welcome back to theCUBE's live coverage of Microsoft Ignite. 26,000 people from around the world have descended onto the Orlando, here in Orlando, for Microsoft Ignite. I'm your host, Rebecca Knight, along with my cohost, Stu Miniman. We are joined by Christina Warren. She is the senior cloud advocate at Microsoft. Thank you so much for coming on the show. >> Thanks so much for having me. >> So I'd love to have you talk a little bit about your work as a senior cloud advocate. And you are responsible for a lot of the video strategy of Channel 9. >> Yeah, I am. So we have a cloud advocacy scene within developer relations, and most of our advocates are focused on either kind of a specific technology area or a specific audience. I'm a little bit different in that I am kind of of a, I call myself, I'm kind of a jack of all trades, master of none. So I go across a lot of different technology areas, but I look at our video content and our video strategies that we have at Channel 9 and our YouTube channel, Microsoft Developer, and some of our other channels, and I think about what are they types of stories we want to tell, what's content do we want to create for our audience, and how can we bring new developers into our ecosystem, as well. >> So what are those stories? I mean, what do you, what are you hearing from customers and what are you hearing also from colleagues at Microsoft that say, "Here's something that we need to tell the world about"? >> Yeah, so I think it's really interesting. I think there are a lot of things. One, there, we were talking a little bit before the show. There's kind of an insatiable, I think, need for a lot of people how to get started, whether it's getting started coding, if you're wanting to learn Python or learn JavaScript or something else, or even if you're just wanting to, you're starting to get into infrastructure, and you're wanting to learn, okay, how do I, you know, spin things up on the cloud. How do I set things up? And having some of that base fundamentals content is really important, but I also think sometimes it's about troubleshooting, and it's about figuring out what are the new services. What can this do for me? And I think a lot of times, when I think about the stories we want to tell, it's not, oh look at how great our service or our product is but it's this is designed to ease my pain points and make my life as a developer or an ops person easier. >> Christina, in the early days, everybody thought that, you know, the promise of cloud was it, it was supposed to be simple and inexpensive, and unfortunately, we learned it is neither of those things by default, so, you know, how do we help people to go from, you know, it's only 20% of applications today are in the cloud. You know, really simplicity is something we need to attack, and education is one of those areas that we need, you know. Give us some examples of some of the things that your team's doing to try to help us get to the majority of environments and work loads. >> Yeah, so a great example is, you know, .NET Core 3.0 launched a couple of months ago, and there's been a big push there with cloud-native apps and cloud-native applications, and so we have like a new video series, The Cloud Native Show, that my colleague Shane Boyer heads up, where they go through kind of all the steps of cloud-native development. And what's great about this is that you have existing .NET developers who have not, to your point, you know, 80% of applications are still not on the cloud, so they're going from that older environment. And then this is saying, you can take the skills you already have, but this is how you think about these things in this new environment. And for a lot of things when it comes to tech, if you're, the way I can always think about things is the next generation of developers, they don't know a non-cloud world. They're literally cloud-first, and I think that's an important thing for all of us to consider is that the next generation developers, the kids who are in high school now, the kids who are in college, they don't know, you know, the pain of having to provision and deal with their own, you know, servers or data centers. They've only known the cloud. And so, but that's an interesting opportunity both to create cloud-first content for them, but for the people who have been using things to say, okay, what you've already been doing, there are changes, but you're not starting from zero, and you can take some of the things you already know and just move that into, into the new world. >> Yeah, well, one of the interesting things we've found this week is that when we talk about engaging with Microsoft, it's not just .NET, it's not just Windows, or Azure. We talked yesterday with Donovan Brown and Scott Hanselman, and it's you know, any app, any language, your tools, pulling those off together. That's really challenging from, you know, creating content out there, because, you know, you're not going to recreate the entire internet there. So how do you tie in what you're doing with other resources and have that, you know, communication, collaboration out there in the industry? >> So a lot of it I think from what I do and what a lot of us do, I look, I used to be a journalist, so I look at what's interesting to me and what stories I would want to tell and what things I would want to know more about. And so, you know, Visual Studio Online, which was announced this week, massive announcement. I'm super excited about that. I am super excited about what that means, and I know that the audience is going to be excited about that. So I look at an announcement like that, and I'm like okay, what kind of content can we work with with those product teams to do? What sort of tutorials would I like to build? What things would I want to know more about if, if I were, you know, really experienced or just getting started? And I think some other areas are, for instance, Windows Subsystem for Linux 2, WSL 2 will be coming out in the future. That's a great opportunity for people who are both familiar with Linux and might not be familiar with Linux to kind of get started and using Windows as their development platform. And so when I see trends like that happening or things around, you know, containers, you know, Kubernetes, you know, containerize all the things, start thinking about, okay, what are the opportunities? What are cool examples? What would I want to see as somebody who, who's tuning in? That's what I always try to think about is what would. I just try to think about it like a journalist. You know, what would an interesting story be to tell from my perspective? What would I want to know more about? And then we can go from there and work with the product groups and work with some of the other teams to make sure that we can tell those stories. >> So, I'm curious. As a former journalist, you spent a decade as a digital editor and reporter and commentator. What made you want to make the leap to big tech? >> You know, okay, so media is not a great place right now. So that's number one. Number two, you know, I was very technical as a journalist, and it was interesting because when I made that transition, I then had to really actually shore up my tech skills. And I said, okay, I have some of the basics, but I really need to like double down and invest in myself and invest in learning more. But I always, even when I was a journalist, I loved telling developer stories, and I loved advocating for developers. Even when I was, I was working at really mainstream places like Mashable, where, you know, they would send me to developer conferences, and I wouldn't just go to the press things. I would want to go to the sessions and talk to the developers and find out, okay, what are you excited about? What are the opportunities you see to build things? What's coming around that has you excited? I've always loved that. And so when the opportunity presented itself for me to be able to do that at Microsoft, I was like, oh, you know, I'd never considered that before, but that's really interesting, and that would be a interesting way of maybe seeing if I can do something else. >> One of the skills that you, that you, is common between what you do now and as work as a journalist is breaking down this technical language and making it accessible for a wider audience, particularly at more mainstream publications. What is your advice for people in terms of how to do that? Because on this show, we have a lot of technically-minded people who can really go deep into technology. But how do you then make it accessible? What is, what is your advice? >> I always try to think of who is your muse as someone who might not know what's, all the intricacies that are going on but is an intelligent person that can understand. So for me, I always use my mom. Now this was easier when I was a tech journalist than it is what I do now because she understands even less what I do now, but I try to think about, okay, how would I explain this to her? She doesn't need to know all of the intricacies, the nitty-gritty. But how could I explain something to her that would be technically accurate but would get the basic idea? And I think a lot of times when it comes to breaking down content, it's just getting to the essence of what problem is this solving, what is this doing that's better or worse, and how does it do it and in starting from there. And it, a lot of times it just takes a lot of work, and you figure out as you go along what getting feedback from users, frankly, based on they might be asking more clarifying questions, or maybe they'll want to know more about something or less about something else. This is confusing for me. And just modulating that as you go along. >> Yeah, Christina, it makes me laugh, actually. When I started blogging, my mother was one of the people that would read, and she would say, "Oh, yes, I heard about this cloud thing before. "I watched it on NPR." It's a nuanced and complicated message. I actually, I roll my eyes a little bit back at the old Microsoft to the cloud videos there, because it was like it didn't resonate. It's the stories that you're telling these days. How do you balance there's the outcomes is, yes, we want to, you know, solve, you know, some of the great challenges and help healthcare, but, you know, underneath, there's some nitty-gritty developer and infrastructure things that get solved. How do you make sure there's the connections between, you know, what the products do and the outcomes? >> Yeah, that's really interesting. You're right, it is a challenge. I think the, the important thing here is not every message has to have all of those components. So you can tell different stories. You could tell one story that's just more focused on the outcome and is just more focused on the opportunity and what's happening in healthcare, and you could have another story that might be about this is what's going on underneath that is allowing those things to happen. >> Yeah, do you, do you have any favorite, you know, outcome stories from Microsoft? >> Gosh, you know, yesterday, during Scott Hanselman's developer keynote, he was, he was, I didn't even know about the Chipotle case study. That was so interesting to me and seeing what they're doing with the different technology. That's, that was a really, that's just the first one that comes to mind I thought was really cool. I'm really excited about the opportunities we have in Quantum, and I'm really excited about opportunities in healthcare because, you know, I think we've all been to the doctor, and we've seen how much IT and how much tech infrastructure could help not just the process of diagnosing and helping things but just, even just the minutia of data entry and record delivery and keeping track of everything. So there, a lot of the things we've done there have been really interesting. >> One of the things you said is you love telling developer stories, and I'm a journalist, too. And I cover entrepreneurs, and I feel the same way about telling entrepreneur stories. Talk about some of the common characteristics you've seen. I mean, we can't obviously generalize an entire population of people, but talk about what you have seen as sort of the common elements of their personalities and their approach to solving problems. >> Right, so I think it's interesting. When I think about any developers, which are a little bit different than enterprise devs, although there are some similarities, you know, you start with, and I know for me when I start first started coding and when I first started building websites and then other things, like, for me, I wanted to either solve a problem, or I wanted to create something that other people could, could see. And so a lot of times that probably one of the more commonalities is, you know, developers, they're in many ways wanting to scratch their own itch. I wanted to do something, I couldn't figure out how to do it, so I built this myself, found out other people were using it, too, and I added features to it. I mean, I think that's what's so great about open-source is that people have the opportunity to collaborate either contributing code or even, you know, doing bug reports and or sharing ideas. And so I, one of the more common elements is I wanted to do something, or I had a really interesting idea, and I didn't see anyone else doing it, and so I just decided to build it myself. It's not that different from entrepreneurs, right. Like it's I see, I see a business opportunity, I see a business I want to do, so I'm going to build it. And that's, wanting to build things is probably the most common thing I see. >> Yeah, Christina, any common conversations or things that are coming up that, you know, people that aren't at this show, you'd like to share? >> Oh, gosh, I mean, I think there's been so much good stuff. I mentioned Visual Studio Online, which I think is really exciting because I'm really excited about being able to like be on my iPad and also code. Like, that's going to be really great. Also, I think the Arc stuff, the Azure Arc stuff is really interesting, the idea of being able to not just be focused on, you know, one platform, but being able to control all of your infrastructure no matter where it is is really, really, that's a really compelling story. That's something that makes me really excited because I love to just automate and simplify things, so anything that can make, you know, the life easier, I think is great. >> As a former journalist, I'd love your thoughts on the state of news today. I know you said you got out of it because it's not a great career path, but the overreach of social media, the spread of fake news, the real and perceived media biases. I'm interested in your thoughts about where we are today, particularly as it relates to coverage of technology. >> It's interesting. I think in some ways technology. For a really long time, most technology coverage was almost cheerleaderish. You could even look back even 20 years when the dot-com crash happened, and I was in high school then, but I was following all of that avidly. The after flow of that, the business press was maybe a little bit burned, but the technology press was still very much gung ho and was still very much cheerleading. That's changed a little bit as we've started to have to grapple with some of the consequences, good and bad, that happened with tech and with the internet. Right now, I almost feel like maybe we've gone a little bit over the edge a little bit more, and some of the critiques are fair, and some of them maybe are just, you know, it's popular to kind of be more negative. So that's been an interesting change, I think to see. You're right, though, when it comes to the spreading of kind of misinformation or people just reading things in headlines, it's really difficult I think, for people to find authoritative voices and things they can trust. Weirdly, though, I do actually think this is an opportunity for the big tech companies to help. This is things that AI could really play a big role in. These are things that could really kind of help, you know, recognize patterns of scan bots and of other things that aren't there and filter that out. But I think even when, I still feel good about journalism as a medium. I still think that the press is one of the most important assets we have, and even when we are going through shakier times, there are opportunities. I think that we will, it'll find it's way. And honestly, I really do think that technology is one of those things that will help get the real things, the important stories out there. >> All right, so, Christina, I guess final word is how should people think of Microsoft in 2019? >> We're here to help. You know, I think that we are, we are a technology company that is, that is creating the tools so that you can build and solve the problems that you need to solve. >> All right, that's a, that's a great note to end on. Thank you so much for coming on the show, Christina. >> Thank you so much for having me. >> Stay tuned for more of theCUBE's live coverage of Microsoft Ignite coming up in just a little bit. (upbeat instrumental music)