![]() They all will work with Visual Studio Code’s Java development tools or with any other OpenJDK-ready Java development environment, simplifying setting up and running a test environment on your PC.Ī build of OpenJDK 11 is already available in the Azure Cloud Shell, so you can use it with jshell to try out code snippets. If you want to work with Arm64, there’s an early access build of OpenJDK 16 for Windows on Arm, so you can start to experiment with it. ![]() Now available for download, Microsoft’s preview build of OpenJDK 11 is for Linux 圆4, MacOS 圆4, and Windows 圆4, with debug symbols for all the releases along with source for your own builds. Since Microsoft offers Java support for Azure App Service, Azure Functions, and Azure Spring Cloud (among others), using OpenJDK will keep their costs to a minimum as Microsoft won’t need to pass licensing costs on to users as part of Azure subscriptions. Using an open source Java avoids complex licensing issues with some Java implementations. Supporting Java on the Azure cloud has brought Microsoft back to Java, hence Microsoft recently announced its own build of OpenJDK 11, targeted at developers working with Java on Azure. Following the public Java SE (Standard Edition) specification, OpenJDK provides source and binaries for Java runtimes and the developer toolkit, with contributions from many different companies and individuals, including Microsoft. If you don’t want to pay for a commercial license, there’s an alternative, in the shape of the GPL 2-licensed OpenJDK. ![]() Java’s convoluted history has led to it being owned by Oracle, which commercially licenses Java development tools and runtimes. So why Java now? It’s all about keeping the costs for Azure-hosted applications to a minimum. And now Microsoft is offering its own open source Java distribution, named Microsoft Build of OpenJDK, more than a decade after Visual J++’s demise. Part two of the story has been Java’s return to Microsoft’s platform, with Java tools for Visual Studio Code and support for Java on Azure. ![]() That might have been the end of the story, if not for Azure and Microsoft’s commitment to “go where the developers are.” That was the start of the first part of Microsoft’s Java story, which ended up the subject of litigation between Microsoft and Sun Microsystems over its support for nonstandard Windows APIs, before being removed from the Visual Studio suite of tools. Of course, at the time, the pranksters didn’t know that Microsoft was already working on its own Java implementation, Visual J++. A couple of weeks ago an anonymous Twitter account told the story of an almost-forgotten Microsoft April Fool’s prank, the 1996 seeding of empty boxes of a “Microsoft Coffee” Java development tool across Seattle. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |