Live from San Francisco, it's theCUBE. Covering IBM Think 2019, brought to you by IBM. Welcome back to Moscone North. You're watching theCUBE's live coverage of IBM Think 2019. This is day three of four days of coverage. I'm Stu Miniman, my co-host is Dave Vellante. We've been talking so much about multi-cloud this week that Pineapple Express has hit San Francisco. Heavy winds and rains, but we're safe and dry inside. They're handing out ponchos and making sure that everybody can still get all the information that they have. Happy to welcome back to the program, Bala Rajaraman, who's an IBM Fellow and Vice President with the IBM Cloud Group. Bala, thanks so much for joining us. Very nice to meet you. Very nice to meet you guys. Thank you again. Very good to see you guys. So it's always, and I mean this, an honor to be able to talk to the IBM Fellows. I've had the pleasure of working with a number of IBM Fellows and of course we've had many of them on theCUBE. It is not just an honorific. It means you've done the work. You've been with IBM for more years than what we'll mention on camera, just to protect you there. But Bala, we had you on the program a year ago at Think. Give us the update as to what you've been working on and as we're speaking right now, the IBM research keynote is going on and I love the connection between what happens at IBM and some of the pure research that happens at universities and that funnel of innovation that happens through the company. That's a great question. I'm glad to be back here and it's been a fairly eventful year, as you guys know. I worked on our public cloud. We worked with a lot of clients and we looked at kind of the dynamics of the market and what is the transition to take advantage of cloud technologies and there was certain, not just barriers, but certain opportunities in terms of looking at things like private cloud and you guys have done some really good work and some of the research there. So private clouds became a point of focus for me and over the last year, working with a lot of clients, the notion of hybrid became really important and hybrid is not just a cloud structure, it is how you actually build applications on top of it. So when you look at some of the announcements around things like Watson everywhere, it is not driven by just having Watson in different places but the use cases it addresses. So things like manufacturing, where you're bringing more intelligence to the edge to the manufacturing floor, but you take advantage of big data analytics on the cloud. How does that work together? How do you address a lot of the technical movements of data, et cetera? And so that was really the great opportunity and insights that we saw and that drove our multi-cloud and public cloud strategy. Yeah, you bring up a really good point. I mean, the application is, the reason why infrastructure existed is to run the application and the data is important and I think back 10 years ago, it was like, well, am I going to burst applications? Are they going to stretch between them and the dialogue has changed quite a bit. It's now with microservices architectures. It's not that my application spread, it's that pieces of applications could live different places. They can live in a multi-cloud. I sometimes might be spinning them up in a geography or time. So IBM has strong ties, has lots of applications that deliver and working in all of these, developer microservices environment. How's this, show me, tell us where the work's happening and what you're doing for users. No, it's a really good question. So I think we really see three movements here. We accept the fact and the market is validated in terms of hybrid cloud, which is you've got pieces running on-prem, you have pieces running on the edge, you've got pieces running on one or more cloud providers. So the hybrid multi-cloud landscape is really a preferred architecture. But that architecture also brings complexity. And the three dimensions of complexity that I see are one around programming models and integration. How do all of these components integrate together from a programming perspective? Because you're choosing different clouds for different reasons and how do those capabilities integrate together? The second element is data. You've got data moving to different clouds, you've got compute moving to data. How does data governance, how does data integration work? And Rob Thomas talked a lot about some of our differentiators there. The third element is managing the environment from a security perspective, from a compliance perspective, from a configurational consistency perspective, from an upgrade perspective, from an availability and monitoring perspective. These three dimensions and the amount of work we are doing in that context, not just in terms of the existing portfolio around integration, but when you look at the complexity of microservices, a number of entities, you really start bringing in elements of AI into the discussion. So how do you enable operations with AI? How do you enable data placement, categorization, governance with AI? So it is, even though it might seem like different technologies, I think bringing them together to solve this problem is perhaps one of the most exciting things that we can provide to the market. So Bala, when it was becoming clear that public cloud was going to be a force, way back when people with large estates on-prem started talking about hybrid, we use that term now, maybe they didn't use it then. But the notion as Stu was describing that you'd have some parts of the workload in public, some parts in private, maybe it is bursting, this was long before EDGE and the ascendancy of microservices and Docker and CoreOS and the like. And then it became pretty obvious to a lot of users, wow, this is really complicated and the use cases just don't warrant the business case. So these things have changed. You, we've seen the ascendancy of these other services. You just laid out three complexities, the programming models, the data movement, which is huge and then how do you manage all that? So how are the use cases evolving? Is the business case more compelling now today than it was 10, 12 years ago? Yes, and I think that's a really, really good question because it takes a problem to the next level. The need for hybrid always existed. It was impractical to look at very, very large complex workloads, transactional needs, to say there was a one solution fits it all, I can move it somewhere. I think expanding and taking advantage of different cloud capabilities is much more of a realistic scenario and a more pragmatic, cost-effective, and it meets many of the business cases. And that's how we got to the 20% though what Ginny was calling chapter one. Yep, so now we have chapter two. Now why is chapter two realistic? Why did, your question was very apropos meaning that there's complexity and when you open up the aperture to more choices, the complexity expands exponentially. What has been really central to it has been the notion of what is, what degree of consistency can I get across all of these elements? And open source, the emergence of things like containers and Kubernetes, not just from a runtime perspective, but from a manageability and orchestration perspective and giving you a foundation against which you can, the consistency that you can take advantage of is been the fundamental revolution of the last two years which has made that intractable problem that we had with multiple choices and the complexity there to become much more feasible. And so if you look at our strategy underpinning those three dimensions of programming models and integration data and management which are not complexities but realistic needs for enterprises to take things into production. The notion of an underlying open multi-cloud hybrid platform based on technologies like containers and Kubernetes and orchestrating across that is the fundamental transformation that has happened. And that is the exciting part is now if it's open, you create an ecosystem, you really address enterprise concerns from how do I build stuff in a consistent way and leverage skills in the market to all the way how can manage it to production goals and security goals. I think we are in the cusp of something that can really transform the way enterprises build applications. And that's what Jenny was mentioning when she said that we are very well positioned to take advantage of the hybrid transformation and the markets behind it. That is the technical underpinnings of why we think we can do it. I'm glad you brought up ecosystem because it's vitally important and you've got a few larger companies. I mean, wouldn't it be nice if we just say I just use one cloud? Well, that's not going to happen. Nope. That's not practical. You'd love it to be IBM's cloud, Amazon would love it to be their cloud. It's just not going to happen. So you have this complexity. Ecosystem is critical. You've only got a few companies that really have the resources to deliver what you describe and to attract the ecosystem. So specifically, can you talk about the ecosystem and how that's evolving from IBM's perspective? So, we're just peeling the onion and I think we're going through a good progression. When you look at development of an ecosystem, the ability to provide choice to an enterprise and the foundations on which it is, the ecosystem is built is very critical. And if you look at the history of ecosystems, it's been built on certain standard programming models or certain APIs. So Arvin keeps talking about things like TCPIP was the foundation of why the internet became kind of a platform. So in a similar vein, when you look at things like Kubernetes, the open standards around it, the ability through all of these orchestration and runtime capabilities to create a variety of choice and the set of choices work together and can be managed together, that is going to create an immense ecosystem. We're already seeing pieces of it, right? I mean, Kubernetes is becoming a model in which many providers are providing the same component across different clouds. You see the adoption of Kubernetes across different clouds. So rather than looking at an individual part of the ecosystem, it is how can we create a broad ecosystem based on open standards, open capabilities, interoperable standards, whether they are formal standards or they are de facto standards. That is what is exciting about this environment. And you're essentially saying that Kubernetes is sort of that analog to old reliable TCPIP here? Is that? Yes, to a certain extent. I mean, I think if I combine TCPIP, HTTP, DNS, how things work together, how things can be managed together, you're coming up with, you're moving up to the next level of coherent standards across every provider. And that set of standards, the things that made the internet work, Kubernetes makes applications work. So networks work together, now applications work together and data works together, which is really. That's a rat hole, Stu, but those are largely government funded standards, which that's a while dried up because people said, okay, hey, we're there. And now this is, you got open sources, this sort of new leverage. Open sources, the engine for innovation. And I think it's a circuitous way to get to that pithy phrase that says open source is the engine of innovation, but that is really the progressive logic that gets you to the fact that it's important. All right, so if we have a solid foundational layer, one of the things, if I think back in my career, 10 years or even 20 years, things like automation and intelligence in my environment, we've been talking about it for a long time. Can you explain why now 2019 is different and how some of these are actually coming to reality more than some of the efforts we've done in the past? That's a great point, because there are two interesting trends that are happening.  You have the emergence of standard platforms. Now it becomes an application game, which is how can I leverage the scale, the availability, and the models of innovation to solve really tricky problems, whether it is supply chains that are globally distributed or enterprises that need survivability in different ways all the way from the clouds to the edge. What are the new architectures possible? But this distribution has also caused complexity. And when you have complexity, you have to bring some of these new technologies into play, like AI and so on and so forth. And so the combination of these three events, cloud, the emergence of open standards that span multiple clouds, and the complexity it creates, but the answers to that complexity that also have emerged is like to me is a very critical point for innovation. I think the landscape is going to look completely different going forward. And I don't think you had the business case for automation, right? You remember, people were afraid of automation. It's like, wow, why should we really do this? We can handle this manually, but today with digital transformation, data, machine intelligence, and the cloud, you can actually make a significant business case to transform your business and drive competitive advantage that you couldn't make 20 years ago. You have no choice but to look at automation today because the scale and that everything's there. And go back to the notion of microservices. You're taking something that you could fence and you could apply certain prescriptive measures to keep it under control. Now you have microservices, you have SaaS systems, you have data that is being dispersed. You have computing that's being dispersed. The only way to take advantage of that agility is to create a different level of being able to understand the systems, secure the systems, and that is going to be driven by new technologies, completely new technologies. All right, so, Bala, you mentioned one of my favorite words, innovation. So, you know, what are you seeing in the cloud, both from IBM, from your customers, from your partners? Where is that incubation for some of those next trends? You and I, as we were prepping this, thinking about like Bell Labs back in the day or the space race, you know, where do we get those, you know, ancillary innovations that help transform industries? How will cloud impact that? I think there's two interesting questions there. One is how will cloud impact innovation? But more importantly, how will innovation impact cloud? Right, and both of these directions are important. So, cloud really gives you the ability to cloud. And again, I look at cloud as kind of in quotes cloud because it includes a variety of easy access to resources, the open source innovation, the ecosystem that gets built. All of them are drivers of innovation. And it gives a way to easily exploit that innovation. I see that as the fundamental value of cloud. Now, the interesting part is there's a whole bunch of other innovations, whether you look at the debater from Watson, or you look at quantum technologies. You look at some of the Watson capabilities that are in conversation. How do those start transforming existing processes? So, when you look at, for example, to me one of the exciting things about debater is when you can process incredible amounts of information, not only to provide insight, but to provide rational insights and rationalizable insights. It is a tremendous innovation. Can that be applied to topics like, why is my network having a problem? And can you actually debate with a system to isolate the problem? The amount of possibilities, when you look at those, how they transform, how you run your clouds, how you run applications in the cloud, how you work across the ecosystem, I think there's tremendous amount of potential. And I think, obviously, with things like quantum, solving a different class of problems, making it easily accessible, solving different kinds of security issues, the potential is the accessibility to innovation with the innovation and how it impacts the foundation that delivers that innovation. I think this is a great marriage right now. Well, I want to give you the final word, lots going on here at IBM. We've seen a year ago, we were like five or six different shows pulled together. We're here at the renovated Moscone Center, thousands of people walking around going to so many different sessions, diversity. Give us a key takeaway for you that you want people to have when they walk away from IBM Think 2019. So, to me, the two key takeaways are one, your observation that everything is coming together is really symptomatic of the change in IBM. We are bringing things together to address complexity, make complexity simple for our clients, to bring innovation to our clients, so that's number one. And that has to be done in an open, in an ecosystem across, not just providers, but across a whole, not only a partnership, but a resource ecosystem, a open source ecosystem. And the drivers of innovation that we are participating in and how we are going to influence that is something that I look forward to as well. So, that's the combination. And it's got to be done through code. I mean, it can't just be services and I know IBM knows this, right? Oh, yes. It's built, it's this company, there's a recent chapter on top of services, but that's a huge opportunity for IBM to take. It's deep industry expertise, codify it through software and code and deliver on that vision. That is an enormous opportunity. Exactly, and the opportunities for code are great because now it's really transforming what new code, what is the potential of code in this ecosystem. All right, well, Bala, really appreciate you coming back, sharing your body of effort that's happening to help pull together and help simplify this multi-hybrid cloud environment. Great, thank you very much, guys. Great to have you again. Thanks. All right, and we're here for another two days, helping to break down all the complexities, go through the nuance, speak to the thought leaders, the customers, the partners. Dave Vellante is my co-host for this segment. John Furrier is here, Lisa Martins here, and I'm Stu Miniman, and as always, thank you for watching theCUBE.


The other libraries, you have exactly what is needed. Anything else that is exactly what's needed to successfully run the software without hassle, it's just there. And then you do your work. So in this situation, you've got this not very fun before. And then you've got this much better after. There's a little bit of toil, but it's not much at all. Previously, you had nine out of 14 steps that were toil. In this scenario, this magical scenario, you can cut it down to just two steps of toil. And your total number of steps is 50% less. That sounds pretty good. You're spending less time on that and more time on what you want to do, on what you need to do. This problem can be even worse at work, because when you get a new job, you have to get a new machine. There are multiple projects that you're working on, concurrently. You've got coworkers who might have slightly different machines. They're running maybe Ubuntu 21.10 instead of your 22.04. And then you check in your change, and it breaks for them. And then you say to them that classic phrase, well, it works on my machine. And you also have to debug it in CI, all of those other things. These same problems that you have contributing to open source, they exist in professional software engineering as well. Assuming, of course, that you're not working professionally on an open source project. In that case, you get the worst of both. So here, more frustrating toil. You basically have to be ops for your own machine. And have you ever met a happy ops person? They're not. They're not happy. And they didn't start that way.  And it made them a little bit unhappy, a little bit grumpy. The thing is, you spend too much time around the software. This was a survey done a few years ago by Electric Cloud, which is now defunct. Pour one out. In an approximately 40-hour work week, 10 hours were spent managing the environment, managing the workspace, libraries, OS updates, all that stuff. And then there was also a lot of time lost waiting for tests to complete because machines might be under-resourced, and similarly, waiting for builds to complete. Now let's imagine a professional scenario. Let's imagine a company, let's arbitrarily call it Redoc. We've got Adriana. She's a new software engineer joining from the lovely city of Florianopolis, Brazil. We've got her new manager, Bia, who works out of Montreal and Quebec. And then we've got Chinwe, who's a VP of engineering working out of Atlanta. This is what Adriana's day one could look like. She opens up her shiny new laptop. She authenticates with GitLab. She loads their instance of their cloud workspace system. She selects the workspace that Bia created. She starts her local IDE. She runs a build and a test, which passes perfectly. And then she starts work. This is done in 10 minutes.  There's no frustration. There's no dealing with all of the little things that get in the way, all of the little rocks in your shoe as you try to walk down your first day. And that's because her manager, Bia, got there on day minus one. She went into the app. She clicked Create Workspace. She chose a shared developer image that had already been created. And that developer image is built on a Linux image that matches their production. Exact distribution, exact version, same kernel version, so forth. It also includes their API server with a database template so that she can run their PostgreSQL, for instance, built in. And it's targeted at the X8664 architecture, which is also what they run in production. Because they have a mobile app, it includes a macOS virtual machine so she can run iOS apps as well. And then, of course, your dev tools, all of this prepackaged in a custom image. You just have to choose it and away you go. And then, just to help Adriana out and make efficient use of resources, she sets it to start automatically, Monday through Friday at about 9 AM, Brazilian time, and then automatically stop 10 hours later. She doesn't want Adriana overworking, after all. And then she changes the owner to the new hire, Adriana. And she's done. Bia did this in a similarly brief amount of time. And now, because of this little bit of effort before, Adriana can get started in 10 minutes. So we can look at Adriana's day one, which in a more typical environment might be the middle of day four. She can make code changes, simple code changes. She adds an additional database column to some lookup query. She passes that field back in an API response. And then she uses it to display a new field in their mobile app. This is 15 lines of code. It's not a huge change, but remember, she's new. She doesn't know the code base. But she's able to get to it by 2 PM with this small change, because of all of the normal new hire craps she didn't have to deal with. She was able to do everything she needed after logging in and starting up her workspace. Sorry, her workspace was already started. So Adriana, the things that she appreciates about this, she doesn't have to deal with out of date onboarding documentation. Who here has gotten a new job and the documentation was completely up to date? And you had to get no help whatsoever setting up the software. Anyone? Really? We should talk. I want to know about the Shangri-La that you lived in. There's no fiddling with library versions. There's no fiddling with additional tools. There's no tracking down all these different dependencies. There's no trying to make them work on her machine, her OS, her version. And there's no risk of breaking anyone else. These are the things that probably go through everybody's mind when they start a new job, because that's what they've had to see. That's what they've had to deal with in all of their previous jobs. But what's nice for Adriana is she just writes code. That's why she's in this profession. She loves writing code to build features. She doesn't love being ops for her workstation. Bea buys into this as well. As a manager, she loves getting near immediate, new hire set up. She loves that her team spends a lot less time investigating mysterious bugs that are caused by subtle differences between deployments or caused by configuration drift over time. That means that fewer bugs escape to production. And then the VP is also pretty chill about this, because there are fewer company level incidents.  OK, this is what happened. This is why it happened. Here's what we're going to do to fix it, because it just happens less, those stressful occurrences.  That's also beefy. She gets powerful budget and policy controls to make sure that people are using the resources they need without overusing and without leaving orphaned resources out there. I think everybody in this room has probably, at some point, seen a cloud bill and wondered, where is that coming from? I thought I shut everything down. I had a cloud bill from AWS for three months for $0.36 before I tracked down what was happening. I thought I'd shut everything down. But you get good policy and budget controls. You don't have to worry about that. And then she also has to worry about compliance and security requirements. And she can satisfy those through the system. Now, you've heard this before. This is like the second time Dolly has ever made a realistic face that's not terrifying. So congratulations, Dolly. What's changed are VMs and containers. There are many, many container and virtual machine images. It's become standard over the last 10 years for VMs and maybe the last, like, six, seven years for containers. There are tons of options widely available for running these VMs and containers, different architectures, different GPUs, different levels of power, low-power CPUs, brute force CPUs. These are easy to customize. It's very straightforward to build a custom Docker image. Even I, as a pointy-haired boss, can do it. And then these are easy to distribute. The tools pull them down automatically. Just point them at a registry, and you have it. The infrastructure has also evolved considerably. There are powerful and varied cloud capabilities. We are all the beneficiaries of Microsoft, Google, and Amazon trying to steal each other's market share. They're building really amazing stuff. They're also a lot cheaper. The cost of cloud has been going down, down, down. It's going to continue to go down. And then if you don't want to go cloud, you have robust software for managing on-premises resources, hardware that you own, or just control. You have Kubernetes, which I think half of the other companies here are doing something with, and other orchestrators that can dynamically provision resources as you need them. For example, when somebody is running a really big build. But then also release them when you don't need them anymore. So you get a level of flexibility here that you maybe couldn't have before. There are also remote capable IDEs. They can run in a browser or on a local thick client connected to a remote workspace. You can do this with JetBrains IDEs, VS Code, RStudio, Jupyter, and more. There's also a problem of big, big code bases. Big SaaS companies have big code bases. They've got so many different services. They've got so many different deployables. I used to work at Indeed, and we probably had five deployables per software engineer, just because the system was so vast. You also have big ecosystems with many dependencies. The great thing is there's a ton of awesome open source software that you can build on in the Java ecosystem, in the Go ecosystem, in the JavaScript and TypeScript ecosystem. But there are so many different dependencies that you rely on as a result. All of this plus more means that your builds download more, they do more, they test more. Much greater demand on resources than your typical application 10 years ago. And then you have to support more architectures. A medium-sized company today, probably deploys on Linux, may have a Windows app, will likely have an iOS app, an Android app, maybe a Mac OS app as well. They have to support three different CPU, well, sorry, not CPU architectures. They have to support three different desktop operating systems and two mobile ones. You have to support x8664, RM64, RM7, GPUs. The hardware proliferation continues. And then you might have specialized use cases using different operating systems, using different architectures that are specialized to internet of things, automotive, network switches, and so forth. All those pictures on the bottom right are a courtesy of Dolly, by the way. And then there are increased regulations and stricter policies. Software is making big decisions. In some cases, maybe criminal justice, maybe it shouldn't. But nonetheless, it's making big decisions. Decisions about that, decisions about whether it should stop, whether your car should stop because of something in the road, big, serious decisions. And so the software needs to be examined very carefully, needs to be built very carefully. Companies, as a result, have comprehensive IT policies, managing their data, managing their code, managing their physical and virtual assets. And then regulators, they too care a lot about this through laws like Sarbanes-Occitly and comparable ones in other countries. And we also have a more threatening security landscape. Laptops get stolen or lost, and that was true 10 years ago, 15 years ago. What is different is people use laptops as the standard computer, where maybe that wasn't the case before, and they're working on software or sensitive data a lot more than they used to be. So this risk has gone up considerably. Hackers will steal code and data from insecure computers, especially on home networks. And then bad actors inject malware into source code so that they can attack the downstream users of that software. I'm sure a number of you are aware of the SolarWinds hack that was discovered in late 2020, which was exactly this kind of supply chain injection problem. And then of course, our buddy COVID-19. Lots of people are remote now and are quite likely gonna be remote forever. I myself know I'm never going to work in an office again. You can have sufficiently powerful workstations for all of these needs, but they aren't portable. And then your portable workstations aren't sufficiently powerful. And that's kind of frustrating, right? Like, why can't you have both? It turns out the future is already here. It's just not evenly distributed yet. Attributed to famed cyberpunk author William Gibson, who might actually have said this. This future is already here for engineers just like you who work at Facebook and Google, Palantir, Stripe, and more, not many more, just a few more, but they've done it. Remote workspaces, they can do what the local ones do. They can host an IDE, they can execute the builds, run tests, run a debugger, they can connect to service dependencies like other microservices or databases, and they can connect to the internet, assuming of course you want them to and you allow that with your network policy. Remote also does what your local workspace can't or it can't do well or it can't do affordably, can't do securely. It'll live in a secure network if you so choose. That limits direct access to data or code because you never have sensitive data or code on a remote endpoint. You access it through a controlled system. It can also provide more resources. You can get many more cores, a lot more RAM, and it provides efficient access to scarce resources. If you tried to buy a GPU a year ago, it was really hard. Gamers wanted them, data scientists wanted them, Bitcoin miners wanted them, and those data scientists use the crap out of them. They run enormous jobs for really important business use cases, for example, at hedge funds. And then it can easily replace workspaces. If yours is acting funky or weird, you just throw it away, build another one. It's trivial.  And then you can switch between different workspaces that are running simultaneously. You can switch between different operating systems and architectures that are running simultaneously. You don't have to deal with local VM software, dual booting or anything like that. You can have two pristine standalone workspaces running completely different operating systems at the same time. It's better in just so many ways. You get more productivity. You get better security. You have an efficient use of resources because you can grab resources when you need them and release them when you don't. You can have consistency through all of your developer workspaces, your continuous integration, your production deployments. You have a lot of flexibility. You can use any kind of operating system that you need or want. You can use any architecture that you need or want. You can configure these workspaces any way you want. You have convenience and portability. It's so easy to get started. It's so easy to switch computers. I write code against one workspace from this laptop and then I also write in the same workspace the same code from my home machine and I switch seamlessly through them. And then you just have less frustration. We get paid well but hassles are hassles. They take away from our well-being. They can ruin our days. They can ruin our weeks if they go on particularly long. And the thing is nobody has ever said to me, I'd rather do this the old way. We have customers that say things like, I'd like this feature or this isn't working right.  I'd rather go back to having an underpowered laptop for these giant builds. What they say instead is I will quit if you take this away from me. So I said the future is already here. It's just not evenly distributed yet. This all sounds like a shell script and a Docker file. It turns out this is much harder problem than it seems. So it's required the resources of a large corporation to get it right. The shell script and Docker file will work until it doesn't. It may not work across multiple people, multiple teams, different architectures. It may not have sufficient flexibility, scalability. And then it leaves a lot of things to be desired in terms of resource management, security. So you can do a very basic form of this very easily, but you run into the limitations very quickly. And the sheer difficulty of this problem means you need to be a company that can have like 50 software engineers just dedicated to develop a productivity. Maybe a hundred, maybe more. Or you can have what they have. Coder is now free under the AfroGPL and it's free in terms of money. You go to github.com slash codercoder or to our homepage at codercoder.com and you can get it today. We made Codeserver, which some of you may have used before. Very popular. This takes what Codeserver does and expands it to a robust comprehensive platform. It's no longer just an IDE in a browser. It is a complete replacement for everything that you do locally on your machine to build software. And it's not just that you can have what they have. It's actually better than what they have. We know this because some of these companies have built it themselves and then wanted to use our product instead. So this means all of you can get a remote workspace. Coder is really convenient. You can share workspace templates among different people on your team or across teams. You can automatically update the images and tools so you're never running an out-of-date operating system or an out-of-date compiler. You can schedule startup and shutdown as desired. So you can always have it perfectly running five minutes before you're ready to work but don't have to worry about it running overnight over the weekend wasting resources. It's also flexible. You can run workspaces on any infrastructure you want. You can run it in the cloud. You can run it on a rack in your closet. You can run it anywhere in between. It'll host Linux, Windows, Mac OS, all at the same time in different workspaces. Sorry, different, haven't come up with the term for this yet, different pieces of compute. And then you can access it via a powerful command line interface, an API or a web UI. And you can use any local machine that you want. I can use my Mac laptop. I can use my home Windows machine. A lot of our engineers use Linux. People have used the system to code from an iPad. You could use a Microsoft Surface tablet. Pretty much anything that has a web browser and optionally SSH can run and use a code or workspace. It's also powerful. You can have multiple workspaces for the same user, either sequentially or simultaneously, specialized for different projects. You can attach arbitrary resources like persistent disks or databases. That means these workspaces can be as permanent as you want them to be or as ephemeral as you want. We don't force a choice on you. And then you can host multiple repositories in the same workspace. Coder is secure. You can run the workspaces where you choose. If you wanna do it on a locked down network that has no connection to the internet, it's perfectly air-gapped, you can do that. We have customers that I can't name who do that. We have audit logging. We have powerful access controls. You can limit or liberate any capabilities on your installation that you want. And if we don't quite have what you want, we're very responsive. We're building fast. Coder is fast. These are some results that Palantir published on their blog about a month ago. They're one of those companies that has giant workspaces. They published two benchmarks, cloning the repository and compiling the code. In their remote workspace, compared to the local laptop that their software engineers were often working on, they could get almost five times as fast a clone. This must be a giant repository if it takes 40 minutes to clone, right? This isn't the type of thing that these large companies are facing. Their backend for this project was considerably smaller, but even there it was 1.7 times faster. And then when it came to compiling the code, and I believe this doesn't even include testing or packaging, when it came to just compiling the code, it was three and a half times faster on the front end, and almost 1.9 times faster on the backend. Imagine how much software engineers get paid, and imagine how much time this frees up for them to do what employers and software engineers want to do, write code to deliver awesome features, instead of waiting, instead of staring in frustration at this very, very long build. You can try Coder right now. Two lines, download our install script, pipe it into shell to run it, and then you can invoke Coder server. This uses an embedded DB, uses an embedded Postgres, so that you don't have to download anything, connect anything. You can easily use an external Postgres if you want. There are more extensive docs available at coder.co slash install. We give you a pretty powerful command line interface, which is prettier than almost every command line interface I've seen before. We have a friendly UI in the dark mode that everybody loves, and very quickly you can be ready to rock. There's the workspace web interface on the left. There's my visual studio code on the right. There's shell access on the bottom right. It looks just like a machine. It can run in a container, it can run in a VM.  The best way to predict the future is to invent it, said Alan Kay, maybe. It's also been attributed to Abraham Lincoln, who definitely did not say it. This is an inevitable future. This is the way things are going. We're 15 years behind many other professions, but there's no getting around the fact that the benefits that they have accrued from the cloud are ready and waiting for us, and we are building this future right now. If you want more information, I have some time for questions now, or you can stop by our booth at G12 in the sponsor showcase area. You can also go to our github, coder.com, and then you have our installation docs at coder, cdr.co, slash install. And there's also the install instructions. So cool, thank you for coming. I think I saw a hand raised in the back. So the question was, can you run coder self-hosted on top of Kubernetes? Yes, you can put coder inside a container that runs on Kubernetes. Do we have Helm chart support for this right now? Okay, we don't have a Helm chart yet, but it's also very trivial to deploy that's something that we worked really hard on to make it this simple to deploy. So you can plop it in a container, run it in Kubernetes. We'll work on the Helm charts. We have them for our previous version, so we know this stuff really well. Yes, so the question is, how easy would it be to have these workspace settings in source control? We built exactly for that. So the workspace templates that you use in our initial release, they're just Terraform scripts. We plan on supporting other infrastructure tools in the future, but they're Terraform scripts. And of course you would wanna keep those in source control. We also have personalization options. So you as an individual using a shared image can personalize your own workspace. We do that through support for revision controlled dot files. You just point us at a Git repo that has your dot files and we automatically pull it down and populate your workspace with them. So you can have your Z shell RC exactly the way you want it. You can have your Vim RC exactly the way you want it. And then there's also a startup script hook. So any configuration or personalization that you want on top of that kicks off automatically when the workspace starts. In addition to that, depending on how your deployment is set up, whether it's a highly controlled one and say a big bank or your own where you let yourself do whatever you want, you can connect to arbitrary registries with arbitrary container or VM images. So you can pull down any level of customization in the underlying image as well. There, it's very much a belt and suspenders and then two other things that hold up your pants approach to customization. Check, check. We have some questions from online. Yes, please. All right. Does Coder support iOS development without a Mac? If I use a Coder on my Linux workspace, can I use an image to get iOS tools and a complier for the apps? We do not currently support running iOS. I'm not sure what's involved in that. With Mac OS and iOS, there are kind of tricky licensing issues. So they're not technical issues. So I believe only one of the major cloud providers can actually offer Mac VMs. There are a couple of smaller providers that can do that, but there are some non-technical hurdles that get in the way of Mac OS support. You can do it. It works perfectly from a technical point of view. Just the licensing makes things a little bit more complicated. I believe that applies to some extent with iOS or I could be making that up. If you have access to a Mac OS machine that can host Coder, you can use the iOS tools that are included with Xcode and similar, but iOS natively we currently don't support. Okay, I have a lot more. Okay, what's the difference between Coder and Codeserver? The difference between Coder and Codeserver is that Codeserver is an IDE that runs in the browser so you can edit your code, you can interface with a terminal, you can interface with a revision control.  It's also typically individual, so you install Codeserver for yourself. Coder is meant to be a platform that can be used, yes, by the individual, but also by a very large organization. Looking over there to make sure I didn't get anything wrong. Cool. What is the minimum requirement to use Coder for five or six people? Yeah, I wanna add something to my previous comment. Codeserver is a tool that you can run on the Coder platform. So if you like Codeserver, great. You can also use it on Coder and it's often bundled with our workspace templates. Getting back to that second question. What are the minimum requirements? Coder itself is very lightweight. It uses negligible CPU, we have a backing database. We don't hammer that database super hard. So running our control plane is very lightweight. You can run it on a very modestly spec machine. One CPU, one gig of RAM, probably less. We haven't actually done any testing to find that lower bound. Where you're probably gonna be more limited for resources is in your workspace. In order to have an efficient running workspace, you want a lot more power, right? To get those fast builds, to get those fast test execution. So that's completely up to you. We provide the control plane. The underlying infrastructure is entirely up to you. You spec it out yourself. It could be a physical machine that you own. It could be something in the cloud. And those resources basically depend on the performance that you want and are willing to pay for. Are there any plans to integrate with GitLab similar to other projects? Yes, there are plans to integrate with GitLab. We can integrate with GitLab for authentication very soon. We can integrate with GitLab for pulling in .files. One of the nice things also is when you are authenticating, or if you have set up an integration with one of these version control systems, when you drop into your workspace, all of the keys are already there. They're already loaded in the session. So you don't have to do any Git authentication, anything like that. You just do a Git clone or a Git pull and it works. So we have pretty decent integration with those things. It exists in our V1 and very soon we're gonna add more than GitHub to our V2. But right now it's GitHub. Sorry, question in the back. The question is, can you use OIDC for user authentication? Yes, we definitely support it in V1 and we have support for it in V2, this open source version as well. How does this work versus say Gitpod.io looks like more feature rich but similar idea? Question mark. Yeah, the question is, oh, sorry, you had it, yeah, the microphone. Gitpod is another company that's in this space. I wanna be careful how I say it because I think they're competent, capable people who are building a reasonable product. I don't wanna sound like I'm disparaging them. But our product is better. One difference is that theirs is a SaaS product. They do have an open source distribution but it's not, I think, front and center. So I don't know how challenging it is to deploy and install. What I've found in my professional experience is when you have a SaaS online type of product, gathering up all the various tendrils of that to make it something that somebody else can deploy and install is very challenging. So they may have run into that problem. They, I believe, have more limited support for different IDEs. They have more limited support for the resources. I believe that you rent the resources directly from them to run workspaces and so you can only use what's on their menu. Those are a few of the differences. So what we've been able to do with our product in part through working very closely with some really big companies is we've made it very flexible, very powerful. We are very unopinionated about which tools you should use, which platforms you should run on, which architectures you should use, which infrastructure you should use. We wanna align to the many choices that you've made to fit your needs. I think SaaS products are less able to do that. Does Coder offer Rasbian support? I'd like to run it from my Pi to do remote development when my laptop is off and it's the closest I have to a machine I can keep running for hours on end. Yes, you can run Coder on a Raspberry Pi. Yes, question there. Yeah, so the question is, what are the networking requirements to connect to your Coder instance? This is one of the clever bits. All you need to do is to be able to connect to the control plane and then through the magic of some sophisticated networking techniques, that can be proxied on the initial connection to this workspace cluster that might be hidden behind a firewall and then we establish a direct machine to machine connection that skips the proxy using turn and stun and things like that. So initially the handshake goes through the control plane but after that you have direct connection without having to punch holes and firewalls or anything like that to your workspace. So you can keep that secure and only expose the control plane to wherever you need to access it from. You can also avoid that if you're particularly concerned by just running the tools and the terminal in the browser. So you don't necessarily have to even access it that way. We tunnel SSH if you need to and anything that builds on SSH can work pretty seamlessly. So local or browser-based as you like. Yes, yeah, so the question is how do we monetize or in another sense like when do you have to start paying? Our overall philosophy is that we want features that are good for the individual software engineer or the small team to be free in our open source project. Where we draw the line where it starts becoming something that we charge money for are the features that most benefit large enterprises. So more robust policy controls, perhaps cost management. We have a long list of things that we've identified that they might be useful to a small number of individuals and small teams, but where they really have the most value is at the enterprise level. We want this to be a full and robust and complete experience for the individual software engineer or the small team. So we're definitely gonna bias and in fact have biased to that use case. So for instance, authentication is one thing that a lot of open core projects may charge for, but as the gentleman in the back asked about OIDC, we support that in the open source product out of the box. So because the individual software engineer and the small team needs that. All right, we are good. Thank you all for coming. If you have further questions, there are a few of us from Coder here or you can visit our booth and we'd be happy to tell you anything about the product, maybe even show you a live demo.


city and in the territory on west there's just one way to handle the killers and the spoilers and that's with the u.s. Marshall and the smell of guns smoke starring William Conrad the story of the violence that moved west with young America and the story of a man who moved with it I'm that man Matt Dillon the United States Marshall the first man they look for and the last they want to meet it's a chance a job and it makes a man watchful and a little lonely this is Frank Knight speaking for the world's most honored watch long gene in the conquest of the Old West men won fame through feats of bravery and daring today things are different but fame can still be won it's wonderful to win a Nobel Prize in science a Pulitzer award in literature an Olympic gold medal in sports in the field of time did you know that long gene watches have worn more great public honors than any other watch in the world this is true the highest authorities have ranked long gene watches as the finest achievement in the science and art of watchmaking yet for a surprisingly modest cost you may own or proudly give a long gene the world's most honored watch the world's most honored gift styled with distinction cased in precious metal promising a lifetime of faultless timekeeping visit your authorized long gene with no jeweler he will be honored to serve you he was gone and tried itself right out of the prairie do you know it just seems like it will be coming across at any time now I sure do hope so I'm dried inside out I got some water left in my canteen you don't know sir it ain't drinking water I need mr. don't it's my feet that's burning now you'll live well sure I'll live there's no question about that but I sure would like to get these boots off and get the soaking guess we're coming to it all right I remember them trees yeah look at there mr. don't these other folks there yeah they're sure aren't why they're never gonna lunch that man well you sure did scare them off firing over the heads that way look right off yeah but one of them isn't come on let's get on there blue sister I will get that gag out of your mouth there was a running couple of minutes it'll finish me for sure you don't look hurting on me I ain't hurt thank you some for that you know who it was I sure I know he's never gonna forget neither what were the names why they're a lawman yeah you asked Marshall out of touch late that's something getting my neck saved by a lawman any objections I guess it ain't something I can be too particular about who are you and over those men I'll tell you Marshall this is something I'm particular about what do you mean they'd my habit to tell nothing to a lawman don't approve of what you might say don't yeah look at here hanging out of his saddlebag let's see just an empty sack Marshall money sack says which top bank on there where what do you know about that I know more than I did a minute ago three men robbed that bank mister you've got three guesses that nature Marshall I don't need more than one about you come on so let's take him in health insurance that pays and keeps on paying mutual of Omaha hospital surgical and income protection insurance plans that pay liberal long-term benefits here's what you need dependable protection that pays promptly low-cost plans by mutual benefit health and accident association mutual of Omaha call your local mutual of Omaha agent listed in the yellow pages all right mutual of Omaha Omaha Nebraska for details on protection that pays and keeps on paying mutual of Omaha pay so promptly it is the first company ever to pay out more than one billion dollars in health and accident benefits in its first fifty years find out how this low-cost protection can help you write mutual of Omaha Omaha Nebraska the Marshall be coming out easy to don't count on it isn't gonna leave me sitting there very long they'll have me out of here right soon you the head man of your outfit you need many folks living who'd argue about that your name is brass Pete brass you heard about me yeah I've heard about you besides that Wichita Bank I've heard you're one of the three states well I'm I shall rise some states I just ain't that time to get around to yet or you just might not make it either I'll have just to bring you some supper wait a minute Marshall what is it you don't want me to get away you'd have done better to let them hide behind his lynching how you figure you'd be better off not me much you you're gonna feel mighty foolish after my boys get me out I didn't notice your boys getting out of that rope this morning boys didn't have time to hear you see a lynching is a sudden thing you borrow a horse and a couple of hotheads want to string you up ain't time for word to get around my boys didn't know there's plenty of time now that's what I mean my boys are real good at figuring they'll study out a real nice plan I ain't gonna be here when my boys comes gonna be real hard on you yeah I'll tell you something mister it might be kind of hard on your boys too just you sure didn't pick out much of a town to get herself locked up in it ain't so bad milk I see two three saloons right down the street there saloons in what we're looking for well as a Marshall's office that sure don't look like much they probably got brass locked up in the back of it hey hey there's the bank we're going anywhere near that bank looks like it'd be real easy listen Jess you got to keep your mind on what we're here for to get brass out of jail that's all sure man sure how are we gonna do it that's what we got a figure you know we could bust in there tonight shooting we could have a horse ready all right you might just get shot doing it like that well if we ain't gonna shoot him out how we're gonna get it we got to learn about this town got to work it out real careful and shooting is easier you listen to me Jess we got to have a plan all right all right where are we gonna get one oh we're gonna start in right here well you said we wasn't looking for saloons not for drinking Jess for listening come on you telling me not to have a drink you stick to bear do we get this thing settled and you drank it slow you here where look out milking boys as soon as you're able to get on your horse you're right right out of town you've got that straight all right sir yes it's half-mapped you see that milk you see that big fella throw that man out of there look like he was a sac-a-mean yeah he's a fella we got out smart Marshall come on let's go in so there could be only one just one that passed the killing grind of Sun and Wind and sand the test that proved this new car wax the finest in the land turtle wax readers digest ad tells the story of the amazing turtle wax protective power that kept cars colors shining bright even in fiery death Valley Sun just one waxing of turtle wax with new Sun stop gives your car a beautiful hard shell finish guaranteed to last up to one full year it's quick and easy to turtle wax your car yourself remember just one waxing of turtle wax with Sun stop lasts up to one full year turtle wax gets a hard shell finish turtle wax gets a hard shell finish turtle wax what'll it be Jen I'll have a shot there's two bears coming up hey barky yeah we just seen that babe Marshall throw a fella out of here Marshall don't know fool around he and the habit of messing up your customers like that if they get acting smart with miss kitty is kitty that's loon gal sitting over there with it I'd be careful how I talked about her misty the Marshall's partial to her isn't he don't like nobody to cause her trouble you're sure about that yeah mr. I'm sure you'd better be sure about it too that's interesting friend mighty interesting miss kitty well thank you but you really don't have to say nice things about me just because I'm going to wait for a while if ain't that a tall wife just pretty if you were staying that's so good yeah that's right jester now see here boys I can stand a little shivery but this is too much especially from you three out boss now kitty it seems to me we're acting in a fine upright manner we're giving you a farewell dinner we're being as nice as we know how yeah that's just it when you all start acting so nice I begin to worry you know it doesn't sound like she appreciates us no matter doesn't it doesn't matter oh well if my company isn't wanted maybe I'd better not ride along with her in the stage tomorrow why you old faker nothing could keep you from coming along with me you're gonna be gone long dog no jester just a couple of days I've had some things to tend to up there and line it for some time figure them as well make the trip with kitty for company but now we better stop teasing her doc she's got not looking all right well I ain't been a dean miss kitty not a particle I know you haven't chester so here you can finish up the pie well say no I yeah kitty those two men that table right over there behind you you know them no I don't why well maybe it's nothing but they've been sitting there staring at us all through dinner so they were listening everything miss Sam maybe I better go find out what's on their minds excuse me a minute you men seem kind of interested in what we've been talking about over there little lady told you huh yeah that's right she told me you know she's mighty pretty shut up just we ain't breaking no law marshal no but if you got any business with me it's better to come straight up with it that's just what we'll do marshal when the time comes we'll come straight out with it father's day is on its way and here's a quick quiz for the ladies what type of man is the head of your house is he rugged in the great outdoors does he help with household chores whichever type he is he's bound to be the old spice type so you and the kids treat him to old spice by shoulton finest grooming aids a man can use give old spice after shave lotion brisk and bracing happiest ending a shave ever had one dollar or something new in sets after shave lotion men's cologne and stick deodorant handy for travel in a bright red box two dollars or splurge with the captain's box five great grooming aids in one handsome box five dollars there's a wide selection of old spice gifts priced from one to seven dollars finest grooming aids a man can use old spice means quality the captain is the most and all the package with the ship that sells the ocean I know about you doctor I'm kind of sorry I thought about making this trip yeah a ride like this doesn't make you want to do much traveling today oh you're right about that feels like a driver's trying to show us how fast he can go yeah I don't think makes much difference kidding a jolt some Joel like this going slow just makes them last long I guess you're right and maybe you heard us Doc how's that we're falling down oh let me see I look out at it yeah you're right it's a quiet kitty what's the matter we're not slowing down with stock it's a hold up hold up don't you worry you won't be hurt just keep your hands up high guess you covered okay man I have nothing of value not you her me now see here don't make me do no arguing come on out miss kitty you come out lady or I'll fix this old geezer so his doctor won't never be able to help him kitty don't do it all right that's better now doc it's your turn don't you hurt him why ain't gonna hurt him none I'm just gonna send him back to God's message for that big marshal I'm not going to leave her better or there ain't no chance for her at all or for you neither going back that's more like you head right back there and tell the marshall that I'm in the mood to do some horse trading what he just went down to Jones's store for a minute just every fancy just about war it's just her I've never seen him right away so you're walking in the office what are you doing back here they've got kitty what who's got kitty they held up the stage for about an hour out of town Matt they're holding her for Pete brass and you've got to do something all right doc all right just slow down I'll tell me just how it happened they held up the stage and took kitty off they say they won't let her go until you turn brass loose now that's all the risk to it well you know who they were no I don't know the names of they weren't hiding anything I could recognize their faces they were the two men who were so interested in us to Del Monica's last night you know where they're holding her no matter don't they just had to have brass ride down the stage rule until he does they're holding kitty now you got to do something about because this mission will let brass out no chest but mr. Dylan they've got me a skin I know they've got our chester well aren't you going to help her man I'm going to try well then let's listen to me both of you now we don't know where they've got her do we know we don't know sure thing that they'll let her go even if brass goes loose well I guess you're right but what are you planning to do wait wait I miss don't we're not likely to hurt her as long as she can be some good to them if they don't hear from me they'll have to try again I've got to wait I'm not sure do hope you know what you're doing yeah so do I Chester so do I me sight tune up the tune up in a can morning sir help you I hope so and you know hasn't got the big up of a kitty car well it's misfire and some some mr. half my plugs are on strike improved case I tune up the tune up in a can and probably your rings are sticking maybe your valves when was that carburetor clean not too recently improved case I tune up the tune up in a can your cars not such a bad shape all you need to tune up a tune up a fifty dollar tune up now relax we'll add a can of case I tune up to your gasoline another can to your oil that'll clean your whole firing zone valves rings plugs carburetor everything mr. you're pulling it on oh no you pour it in dollar and a quarter a can at most any service station results guaranteed or double your money back improved case I tune up the tune up in a can you're glad you decided to do the cooking miscarry maybe you'll choke on it and it'll be worth it see me like you're acting too friendly any reason why I should sure miss kitty you and me you and me that's the way it's going to be it's never going to be like that you kind of cotton in that big marshal that's none of your business you think he's going to get you out of this you'll be here sure you're gonna be here milk went down to talk to him make sure he'd be here I know that then we both know it I know something else don't you want to hear about it not much you better want to I done me some figuring milled ain't the only one to do the figuring they thinks he is sure he does this time I done some figuring all by myself I got it all worked out about that big marshal what do you mean even if he comes even if he lets brass go he ain't going to get you how do you plan to stop them well ain't nothing to it after the figure is done that I just ain't going to let him ride out of here that's all we're already getting pretty close now Mr. Dillon yeah trust it brought along in here you think they'll really show up with Miss Kitty how about they want this man they will he really got you squirming ain't they marshal don't worry about it brass I told you my boys that study it out they haven't finished it yet Dylan there under them crease yeah come on look here I can see Miss Kitty and one of them fellas just keep your eyes ain't nothing wrong with me let her go you're gonna need your hands to dig two graves with for your boys sir put down that guy okay honey mr. Dylan told me to pray oh I don't care what Matt Dylan says Mrs. Dennis Weaver says no guns in the house but mr. Dylan told me oh here's our picture and look magazine and it says Chester of Gunsmoke and his wife known in private life as mr. and Mrs. Dennis Weaver mr. Dylan told me how does Maverick practice fast draws around the house no he helps his wife cook dinner well now ain't that something oh here's your old friend doc here and look and the rifleman and there's Yancey Dellinger forever more well ain't there wives pretty though you know everybody ought to get luck and take a look at them cuz you know that girls was made to be love you show Matt Dylan a copy and let him see what other Western heroes and their wives do around the house all right music lover I'll be seeing you were you going down to the newsstand about copy of new issue of look magazine why well for mr. Dylan directed by Norman McDonald stars William Conrad as Matt Dylan U.S. Marshall story was specially written for Gunsmoke by Marion Clark with editorial supervision by John Meston featured in the cast with Harry Bartell Vic Parran James Nussar and Ken Lynch Harley Bear is Chester Howard McNear is Doc and Georgia Ellis is Kitty this is George Walsh inviting you to join us again next week for another story on Gunsmoke latest news follows then Mitch Miller with tonight's guest stars on the CVS radio network