News

Who Says Microsoft Doesn't Do R&D?

Microsoft Research projects drive innovation in development.

Microsoft gets a lot of grief from critics who claim that the company innovates primarily by appropriating the ideas of its competitors. But the world's largest software maker is hardly sitting around waiting for "The Next Big Thing." So says .NET expert Ted Neward, who gave a session about some serious Microsoft-originated innovations at this year's Software Development Conference & Expo West (SD West), held in Santa Clara, Calif.

"How many of you have looked at C# 3.0?" he asked. "It turns out that C# 3.0, a large of part of which we now call LINQ, was originally a language called C omega. This was a language that was on the MS Research Web site, and had some very interesting ideas unifying the type systems between the relational database and the XML. And this idea of this simpler components model, what Microsoft now calls chords, [came] out of that research."

Parade of Innovation
Neward gave other examples: F# is a new functional/ object hybrid programming language that came out of Microsoft Research (MSR), as did Joins, a declarative concurrency library based loosely on the C omega language. Fugue, a powerful tool for specifying and enforcing resource and state-machine protocol specifications, is a child of MSR. So is Detours, a library designed to make it easier to hook calls made to DLLs. Abstract IL is an MSR library created to make it easier to manipulate compiled .NET assemblies. Finally there's Phoenix, a software optimization and analysis framework that will be the basis for all future Microsoft compiler technologies.

Much of what Neward discussed is not commercially available. "Which is to say, you can't ship code with it. But you can use it for your own purposes," Neward said.

He cited the IronRuby project, a .NET implementation of the Ruby programming language. The dev team is using Spec# -- a design-by-contract tool originally inspired by Fugue -- internally on that project. "That's a real-world use that you can't technically ship with," Neward said. "When they ship the final IronRuby, they've compiled it with the standard C# compiler; they use the Spec# compiler only internally. Nothing prevents you doing the same."

Fugue is available for download now for non-commercial use. The Phoenix SDK, pre-release 2007, is also available for download, with another release expected in March. "There's a lot more going on at MSR than we can cover here," Neward said. "But this is the stuff that might make a difference to me as a programmer."

About the Author

John K. Waters is the editor in chief of a number of Converge360.com sites, with a focus on high-end development, AI and future tech. He's been writing about cutting-edge technologies and culture of Silicon Valley for more than two decades, and he's written more than a dozen books. He also co-scripted the documentary film Silicon Valley: A 100 Year Renaissance, which aired on PBS.  He can be reached at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube