Questions for 6/22?

<blockquote><a href="#285677"><em>In reply to inlocoabsentia:</em></a></blockquote><p>Hey, listened to the question on the show, yes there really isn't a case for developing new green field services solely for Windows Server and over time it will be that thing you run only Active Directory / Exchange on.</p><p><br></p><p>There reason for why is because :</p><ol><li>other solutions have gotten good enough and/or are cheaper. </li><li>Non Windows VMs on cloud providers are significantly cheaper than Windows VMs</li><li>The shift to Platform as a service, has abstracted away the many "server" things. When you deploy to AppEngine, Azure App Service, Heroku etc, you don't need to worry about the server side of things. Your code "just runs"</li><li>Everyone is moving to SaaS model, the need for Windows Server became less, you didn't need it to run Exchange, Dynamics and Lync anymore.</li></ol><p><br></p><p>You can still develop on a windows machine with .Net Core and Asp.Net Core, they will run on windows perfectly fine. But now you can run that same code on Linux, when you can run your code on Linux, you can containerise it, you can run it in another cloud that does not run windows, you can take advantage of cheaper VMs since they're not paying a Windows Server license fee. You're now competitive with developers of other languages, who have been able to run on Linux and who have been developing containerised applications.</p><p><br></p><p>These cross platform moves, aren't about killing Window Server, Windows Server dying naturally, it's to allow their existing C# and powershell developers, write the code they know how to write for years on other platforms.</p><p><br></p><p>I started as C# Windows phone developer, then did ASP.Net for Web, now I am a microservices developer using .Net Core, docker and kubernetes. While still being able to use the language I prefer the most. As a dev, I have not cared about the server I'm running on, only if my code can run there.</p>