News

Microsoft Loses Top C # Developer

Eric Lippert was a key part of the Roslyn compiler-as-a-service project.

The defections of top-level people in Microsoft's developer division continued recently when a key C# manager announced his imminent departure.

At the end of November, Eric Lippert, a longtime Microsoft employee and the principal developer on the C# compiler team, announced that he was moving on from Microsoft. Lippert is joining Coverity to work on its static analysis tools.

Many developers were caught off guard by Lippert's departure. In particular, what it means for the future of C# and the compiler as a service project (codenamed Roslyn). Lippert had served as the visible lead of the Roslyn Project. The third Roslyn CTP, which can be used on Visual Studio 2012, was released in September.

The former MSDN Fabulous Adventures in Coding blogger is now blogging at ericlippert.com. He addressed some of the concerns in response to a reader comment on his new blog on Thursday:

 "I am just one of dozens of people working on Roslyn; I'm just the most visible of them. We have heavyweight architects like Neal Gafter and Matt Warren working on this thing and a whole team of smart compiler and IDE people. I am leaving it in extremely good hands and extremely good shape."

In the same response, Lippert said:

"C# will continue to be influenced by me, just less directly. I'm hoping to maintain close ties to the C# team."

Several high profile people have left the Visual Studio and .NET teams of late, including the former head of Visual Studio, Jason Zander, who moved to the Server and Tools Business (STB) at Microsoft immediately after the Visual Studio 2012 launch in September. He is now the corporate vice president of the Windows Azure development team. 

People often switch jobs but it's hard not to wonder, what these changes could mean for Visual Studio and its related frameworks. 

About the Author

Kathleen Richards is the editor of RedDevNews.com and executive editor of Visual Studio Magazine.

comments powered by Disqus

Featured

  • Full Stack Hands-On Development with .NET

    In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.

  • .NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

    "We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

Subscribe on YouTube