Mads Torgersen, the lead designer of C# at Microsoft, remembers “Project Roslyn,” which built an open-source, cross-platform compiler for C# and Visual Basic.NET “in the deepest darkness of last decade’s corporate Microsoft:
We would build a language engine! A unified, public API to C# code: We would redefine the meaning of “compiler”. Of course, once you are building an API for the broad C# community, it is kind of a slam-dunk that it should be a .NET API, implemented in C#. So, the old dream of “bootstrapping” C# in C# was fulfilled almost as an accidental side benefit. Roslyn was thus born out of an openness mindset: sharing the inner workings of the C# language for the world to programmatically consume.
This in and of itself was a bit of a bold proposition in what was still a pervasively closed culture at Microsoft: We would share this intellectual property for free? We would empower tool builders that weren’t us to better compete with us? The arguments that won the day for us here were about strengthening the ecosystem and becoming the best tooled language on the planet. They were about long-term growth of C# and .NET, versus short term monetization and protection of assets for Microsoft. So even without having mentioned open source, signing up for the cost and risk of the Roslyn project was a big and bold step for Microsoft….
F# released already in 2010 with an open source license and its own foundation — the F# Software Foundation. The vibrant community that grew up around it soon became the envy of us all. Our team pushed strongly to have an open source production license for Roslyn, and finally a company-wide infrastructure emerged to make it real. By 2012, Microsoft had created Microsoft Open Tech; an organization specifically focused on open source projects. Roslyn moved under Microsoft Open Tech and officially became open source… C# language design and compiler implementation are now completely open processes, with lots of non-Microsoft participation, including whole language features being built by external contributors.
Torgersen’s article says C# now enjoys “the scaling of effort via contribution of features and bug fixes, but also the insight and course correction we get through the instant, daily feedback loop that open source provides.
“It’s been a long and wild journey, and one that to me is symbolic of the massive changes that Microsoft has undergone over the last decade.”
of this story at Slashdot.
Source:: Slashdot