For years Windows and Linux have been rival development and runtime environments used by two distinct development communities – .Net vs. J2EE. At least that’s what we thought. In fact, they are not rivals at all, really. Rather, they are both commonly used by nearly all enterprises to develop and execute the applications they need to run their businesses.
Today, those applications are being modernized, containerized and redeployed across multiple clouds. Business and IT planners alike are rethinking how to develop new cloud-native applications and the infrastructure needed to deploy them to their best execution venue whether on-premises, in or across private, public or hybrid clouds. They expect the IT vendors and service providers they use to do more than just coexist. They expect partnerships dedicated to customer success – and none more so than among the two leading vendors in each community, Microsoft and Red Hat.
In this webinar 451 Research Principal Analyst Carl Lehmann, Nicholas Gerasimatos of Red Hat and Jose Miguel Parrella, Sr Product Marketing Manager for Open Source at Microsoft will address:
– How to overcome common challenges of application modernization, infrastructure management, and cloud deployment.
– The partnership, and capabilities enabled therein, between Microsoft and Red Hat.
– How Microsoft Azure and Red Hat ecosystems support and complement each other.
Participants will learn how Microsoft and Red Hat build upon each other’s strengths in container-based, cloud-native application development, infrastructure deployment and operations to better serve their mutual customers through joint business practices, technology support, and ecosystem.
Carl Lehmann – 451 Research Principal Analyst, Nicholas Gerasimatos – Red Hat, Jose Miguel Parrella – Microsoft Jun 29 2017 | 58 mins
On Microsoft’s own Azure cloud, 75% of machines run Linux. These are Microsoft customers who are running Linux. Microsoft needs to support the platform they use, or they will go somewhere else.
To that end, Microsoft has written a Linux subsystem in Windows, that allows users/admins to run bash commands.
Is Microsoft’s victory a loss for traditional Linux vendors? To some degree, yes. Microsoft has become a direct competitor. But the clear winner here is Linux.
Microsoft doesn’t own any Linux technologies. They are totally dependent on an external vendor, in this case Canonical, for their entire Linux layer. Too risky a proposition, if Canonical gets acquired by a fierce competitor.
The lines between open source and proprietary software are blurring. Increasingly organizations are building even in-house technologies with open source methods. This includes Microsoft.
From participating in Node.js, the Core Infrastructure Initiative and other Collaborative Projects at Linux Foundation to its recent partnerships with Red Hat and SUSE, Microsoft is demonstrating a sincere, smart and practical approach to how it builds new technologies and supports its vast customer base
Today’s customers live in a multi-platform, multi-cloud, multi-OS world – that’s just reality. This world brings new challenges and customers need tools to make everything work together.
Microsoft announced today that PowerShell is open sourced and available on Linux. (For those of you who need a refresher, PowerShell is a task-based command-line shell and scripting language built on the .NET Framework to help IT professionals control and automate the administration of the Windows, and now Linux, operating systems and the applications that run on them.)
While it’s no longer news that Microsoft wants to cooperate with the open source community, it’s remarkable that Redmond is now going so far as to help found an open source project whose goal is to erase platform lock-in for programming. In the past, platform lock-in constituted the crux of Microsoft’s business strategy, but those days are long past.
Need to edit your defined names in Excel 2016 for Mac? No need to search the Office help site, you won’t find Mac instructions. The short answer is that there isn’t a name manager button on the formula ribbon. The work around is to hold CMD+FN+F3