Microsoft recently established a .Net foundation and open sourced substantial parts of the popular programming language, continuing to spread its newfound love for open source software. However, it’s another movement — devops — that may be more of a driving factor in Microsoft’s .Net move.
In establishing the independent .Net Foundation and making more key pieces of .Net open source, Microsoft was promoting collaboration and community, it said. Many open source technologies exist for .Net, including the recently released .Net compiler platform codenamed “Roslyn.”
Microsoft also highlighted the value and innovation that comes from broader community collaboration, even on its own developer tools and technologies, such as .Net.
The fact that Microsoft recognizes the power of open source software is not remarkable — the company has been working actively to change its thinking and strategy on open source software for years now.
What is interesting is the establishment of the foundation and the further opening up of .Net, which highlights how Microsoft technologies, including Windows, Azure and .Net, all have become part of the devops movement — a trend referring to faster software releases based on collaboration and efficiency among developers and IT operations teams.
This is quite a contrast to the devops landscape that existed three or four years ago. Back then, when Windows admins would dare to speak up or ask questions about how they might get more agile and join the devops movement, they were told to switch to Linux.
Today, most devops tools and providers have integrations, plug-ins, and support for Windows management. Indeed, I have written previously about how the support for Windows in devops tools — such as the Chef and Puppet configuration and provisioning automation software applications — reflects the extension of devops to more mainstream enterprises, where Windows and .Net are common.
The PaaS Piece
We also have seen .Net rise in the polyglot programming trend: A much greater variety of languages, databases, infrastructure and other technologies are used in developing, deploying and managing applications in today’s market.
While most PaaS platforms have become polyglot and support a variety of languages, the enterprise world is still largely a matter of Java and .Net. Thus, .Net has become an important part of PaaS, particularly private PaaS aimed at enterprises.
The 2013 acquisition of .Net PaaS player Tier 3 by CenturyLink is evidence of this, as the acquirer sought to offer a complete set of outsourced IT services, from hosting to enterprise cloud. Prior to acquiring Tier 3, CenturyLink made a similar move in by acquiring polyglot PaaS player AppFog.
Further evidence of a Microsoft and .Net presence in devops comes in the form of added support of .Net among PaaS providers, including Red Hat with OpenShift.
Although Microsoft’s proprietary programming language may not seem like a good fit, Red Hat had been fielding inquiries about working with .Net on its OpenShift PaaS since it launched the service. So, with help from Uhuru Software, which focuses on .Net and Windows support on open source cloud platforms, Red Hat set out to provide more choice to its OpenShift users. The prevalence of .Net applications among enterprise organizations also drove its support of the Microsoft technology, Red Hat said.
The most obvious reasoning for Microsoft’s establishment of a .Net foundation and further opening up the technology is the continued presence and prominence of open source software — and openness in general — in key, fast-moving enterprise IT trends including cloud computing, Big Data and devops. Indeed, in 2012, when Microsoft spun off its open source-focused subsidiary Microsoft Open Technologies, it cited emerging opportunities in open technology — including cloud computing and devops — as the reasoning.
Today, Microsoft continues to reshape its approach to open source software, complete with new CEO Satya Nadella, who replaced one of the world’s greatest open source opponents, former CEO Steve Ballmer, earlier this year.
Though there typically is no shortage of pushback against Microsoft when it makes open source moves, the skepticism and suspicion seem to be giving way to technicality and practicality, both within and outside of Microsoft. By continuing to promote openness, integration and true collaboration with other vendors and technologies, including open source, Microsoft is doing its part to ensure its place in key trends such as cloud computing and devops.
I don’t think it is really open…
The last I knew subsets were not allowed…
And the "patent promise" only if you used Windows… no other platforms acknowledged.
and they didn’t open significant parts of .net.