 Live from San Francisco, it's the Cube, covering Red Hat Summit 2016. Brought to you by Red Hat. Here's your host, Brian Graceley. Welcome back to Red Hat Summit. We're here in San Francisco, Red Hat Summit 2016. 5,500 people here on day two. Excited to have Todd Mancini, Harry Maurer from the app development team. Guys, welcome to the show. Thanks. Thanks for having us. So one of the big parts of Red Hat Summit now is DevNation, the application development piece of it, attracting developers. You guys are a huge part of that. Give us, we've been covering day one and day two. DevNation was sort of pre-show. Give us the highlights. What went on? What were you communicating? What did the community look like? Sure, so we started the day with, we had the morning keynote where we made a number of announcements. It was probably, I think, one of the largest single day announcements that we've had, especially from the developer tools group. And then this is our third year and it's been getting bigger and better. I think this year we had over 50 speakers and 60 sessions and 70 hours of content. So it was one of our best DevNations yet. We made them, it was pretty good. Yeah, let's do a real quick rundown. What were the big announcements and what are the areas of applications they hit? Yeah, sure. So we made a number of announcements. There was really two areas. It was announcements around technology that we've been committed to for many years. And so the first section was we made announcements around support for OpenJDK on Windows, a new type of evolution of Enterprise Java with a micro-profile announcement. And we also announced some new products like DevSuite and DevStudio and if you want to talk about those. Sure, so one of the products that we announced, we didn't actually get a chance to talk about much because we were kind of running out of time, was Red Hat Development Suite. And this is a brand new product and what it actually does is it takes all of our other developer tools and kind of puts them in one package so you can install it super easy and it doesn't only make it easier to install them but it integrates them all together so they work seamlessly together. So I think it's gonna make experience for developers. So I'm no longer bouncing between tabs, it's just a right click or something that's just gonna get pulled in and one experience or one IDE, excellent. And then the other couple things.net core now open source part of REL, part of OpenShift. You guys both have some background at Microsoft. How big a deal is that? What does that mean to the market? It's huge, I mean, from my perspective, I've been at Red Hat about a year and a half and I had left Microsoft, I'd spent a long time at Microsoft and I thought I had left that world and that world seems to have followed me here so it's pretty interesting. But it was a huge announcement for us and it was actually part of that second way of announcements, you know, the kind of the future moving forward for Red Hat and the development space. And, you know, we were really excited. We had Scott Hanselman from Microsoft do the announcement and do the demos along with Todd. And, you know, it's great because we're the first Linux provider to actually have a fully supported version of .NET. So if you're a .NET developer and you want to do it on Windows or you want to do it on Red Hat Enterprise Linux, you're going to get the same level of support. And yeah, it's fantastic. Right, and I got to imagine, I mean, we had Paul Cormier-Anne was talking about Linux and containers. This is going to make it easier to take advantage of those environments, take advantage of microservices. Yep, and we showed some other demos of some tools that were starting to get more integrated with some upstream projects, one in particular, Eclipse Che, which is really container-based development environment. And, you know, Todd did some demos with Tyler Joule from Code Envy around that. I mean, do you want to talk more about Che at all? Yeah, so Che is, it's really unique in its approach to how a developer actually didn't get started. It's completely browser-based, right? So you don't need to install anything. You can be up and running instantly. But where it kind of goes even further is, most developer tools, you know, they refer themselves as an integrated development environment. But really, they're integrated development tools. They don't really provide the environment. Che goes further. It really does have this notion of these universal workspaces. So that not only can you start coding, but you have an environment in which to code, a container-based environment. That includes a full stack of your application platform in it. So it's really, really powerful. Yeah, it's a huge piece. I mean, we talk to a lot of customers and a lot of CIOs are saying, hey, look, I'm seeing all these things happen in the marketplace and Uber's going fast, and Airbnb, and we want to go fast. And then they go, how do I go fast? How do I, you know, writing code isn't, it's getting easier, more people are doing it, but, you know, those big steps that you're making are going to make it easier and easier. And I think one of the things that we heard was sort of citizen developer and this idea that more and more people that aren't hardcore coders can help make an input into that. Yeah, and I think Che plays a lot into that. That's why it's going to be a big part of our strategy. Because, you know, one of the biggest pain points is just getting started, right? It's just setting up your local environment. It's getting everything you need to get running. You know, moving to this type of technology alleviates almost all of that. And so it's really big space. It's getting, taking the friction from sort of idea to execution in terms of that. At least getting idea to, hey, let me test out my idea and see what it looks like. You know, and also part of that too is, you know, Che is really great because along with that, developers are using more and more different types of technologies and languages. And so Che supports a wide, will support a wide range of languages because we also made an announcement with Microsoft around a language server protocol which allows language developers to create standard implementations of their language capabilities that can be plugged into both our development tools as well as Microsoft's development tools. And I think that's really exciting because as new languages and technologies come online, they can easily find a home in these development tools and people can develop their tools. So is that about sort of making a consistent experience for a Linux developer and a Windows developer or is that a Go developer and a Java developer? What does that mean in reality? Yeah, I think it's, yeah. I would actually say it's not about making it be consistent. It's actually about making it so you have that choice. Okay. Right, if we made it consistent, then all the tools would be the same and why bother, right? But the idea here is you get to choose your tool that works the way that you prefer but you don't have to abandon the languages you want to use. Gotcha. In Shea, if you want to do C-sharp.net development, you can, and if you want to do Java development, you can. Same on the Visual Studio side. It gives you the option to now use these languages. And then you guys deal with the ugly plumbing behind the scenes to make it simple and frictionless. All sorts of ugly plumbing. So let's shift gears a little bit. One of the guys in your team ran the demo today. Huge demo. In terms of breath, we had front end development, we had mobile development, we had reactive environments. Give us a sense of what did we see? What was, what all was going on there? Yeah, we call Burr the demo magician because it really is a magic act up there. I mean, you saw, what you saw was someone take code, an idea, code it and bring it all the way through an automated process out to production. You actually, for those that weren't there, it was based around a mobile game. So everyone had a chance to actually play the game. And while during the people playing the game, we were actually making real time changes as it was happening. And you could see it all go through the pipeline up on stage and everyone asked, how much of that was fake and how much was real? It's always all real. I mean, that's the amazing thing about those demos every year. No net. Everything without a net, yeah. Everything without a net. And I think that the big thing that people don't always understand is, you talk about those changes, those changes could be based on a lot of things. They could be based on planned code changes. They could be based on user input that people are going like, oh, everybody's using it this way. Let's make a change. Maybe you want to introduce an ad component to it. You want to introduce a new payment system. People have to be able to change those on the fly. The six month outage window is no longer part of business anymore. No, and actually part of what we showed, and I don't want to talk more about this, but we showed the different types of deployment strategies, how you could do either take the new stuff and just make it 100% of the deployment, or we showed something called a Canary deploy where you only deploy to a percentage of the audience in real time and you test to see if there's any issues. And there's no issues, and it automatically go to the rest of the users. And so, all sorts of feedback happens in real time to make deployment decisions. And that's what we're trying to show you. Sometimes they call those blue-green deployments or retail people call them AB types of testing and so forth. And the capabilities now are, integrate continuous integration, integrate containers so that it's easy for developers. And that part was very, very interesting to be able to say, look, we all talk about these big, kind of PowerPoint slides and here's what's going on. You guys really showed the breadth of that. And what was really interesting was, all of that is Red Hat innovation, Red Hat technology, and then open source technology as well throughout the thing. Yeah, if you looked at the different technologies, we used the mix of production, the products that we offer support for, as well as some new upstream projects like Vertex. And from the container perspective, I thought it was really neat how we showed Che, everything that when Joshua, the first person who was doing the coding, we actually opened up his development environment. It was the same container-based environment that the production people were using. And as a matter of fact, it was the production people that gave that to Joshua, right? It was no longer, I didn't have to worry about my local environment being mismatched from production. And that's a huge problem today. I mean, I think the thing, the big thing I took away from it was, it's sort of like you said, as a developer, I didn't have to really change anything. I'm going to write in whatever framework or language I like, but that consistency of environment went from the laptop to the testing environment to production, could be running in the public cloud, could be running in private cloud. I mean, that's a huge change, right? You no longer have to, it's less finger pointing, less sort of coordination, it just sort of works. Yeah. I mean, part of that, I mean, I don't know if you want to talk about that. There was a mix of technologies across micros, all those different microservices, and there wasn't just one static monolith, Java all the way through, it was actually a bunch of different technologies. Yeah. What's been your big takeaway so far this week from developers that you've talked to, feedback they're giving you, things they still want to see Red Hat work on? Wow, there's been a lot. Some of the announcements, I think that surprised us, it got people really jazzed up, the fact that we have an open JDK now available on Windows that has the breadth of support of Red Hat behind it, that people were blown away by that, and they were super excited about it, because it really helps them address a really fundamental issue. We talk about this issue of, hey, is development the same as production? And then the reality is for a lot of applications that are being written today, say in Java, it is fairly common for a developer's desktop to be a Windows machine, because they're in an enterprise, enterprises deployed Windows out to the desktops, but there was always a concern that, well, what if the JDK that I'm running on my desktop environment, it's different than the one that's in production? Are they going to behave the same? How do I know that? Right, right. And so Red Hat now is addressing that with our distribution of the open JDK, gives you that guaranteed consistency between the Windows and Realm installations. So that it runs on my desktop thing is not just it's in a Docker container, it's also the framework, the runtime, you've got to have a level of consistency of that whole stack. Yeah, I mean containers are really exciting and they're the new thing, and developers will start to use them more as we progress, but today, it's a small percentage that are actually doing development in containers, we still have to worry about that local experience. Yeah, so I'll give you guys the last word, each one of you, sort of, what's the takeaway you want people who maybe aren't here at the show to go, if I'm interested in app development, if I'm interested in just open development, what should they look for from you guys, what's on the horizon maybe that they should be kind of getting excited about? Well, the first thing I'd ask them to do is go to our developer program, developers.redhat.com, come to the site, register, all the products are available for you to use, for free, for development use, and get started. I think the big takeaway or the big message that we were trying to give developers this week, at least through DevNation was, we're really committed to the technologies that you're using today, and we're going to be supporting you throughout, no matter how you use them, but we're also looking at ways to bring you into the future and be more productive in this new world of microservices, containers, and cloud environment. Yeah. And I just add that we're an open by default organization. We really highlighted some of the stuff that we're delivering today, but we've got tons of new stuff that we're working on, and if people come to developers.redhat.com, they can find out about it, and not only find out about it, but start to contribute and get engaged in it, so we look forward to that. Yeah, that's great, guys. Todd, Harry, 10 years of application development here at Red Hat Summit, a lot of new things coming out, Linux and Windows kind of working together, all open source, open application development across the cloud. With that, we're going to be right back. We'll be back all week and all day today on day two here at the Red Hat Summit 2016, here in San Francisco, this is theCUBE.