Phil Haack quit Microsoft for GitHub
haacked.com
Phil Haack quit Microsoft for GitHub
1–10 of 127 posts
Re: Phil Haack quit Microsoft for GitHub
#2Re: Phil Haack quit Microsoft for GitHub
#3- MS Lead on ASP.net MVC framework vers. 1 through 3 (current)
- Lead on the NuGet package manager framework for Visual Studio
- This Developer's Life Podcast with Scott Hanselman
Re: Phil Haack quit Microsoft for GitHub
#4Big loss for Microsoft.
Re: Phil Haack quit Microsoft for GitHub
#5For anyone curious about any background on Phil Haack. Here are his notable accomplishments. - MS Lead on ASP.net MVC framework vers. 1 through 3 (current) - Lead on the NuGet package manager framework for Visual Studio - This Developer's Life Podcast with Scott Hanselman
Re: Phil Haack quit Microsoft for GitHub
#6For anyone curious about any background on Phil Haack. Here are his notable accomplishments. - MS Lead on ASP.net MVC framework vers. 1 through 3 (current) - Lead on the NuGet package manager framework for Visual Studio - This Developer's Life Podcast with Scott Hanselman
I think This Developer's Life is hosted by Rob Conery.
Re: Phil Haack quit Microsoft for GitHub
#7This is awful news for .NET devs- ASP.NET MVC is the best thing that's happened to ASP.NET since it began. Losing the lead guy on that project is worrying.
Re: Phil Haack quit Microsoft for GitHub
#8Big loss for Microsoft.
It could be a net gain for Microsoft if the Windows developer community begins to embrace github. As long as the most talented in the community don't leave the Windows platform, it could lead to a more vibrant and productive Windows developer community.
Re: Phil Haack quit Microsoft for GitHub
#9Re: Phil Haack quit Microsoft for GitHub
#10Earlier quoted context omitted.
It could be a net gain for Microsoft if the Windows developer community begins to embrace github. As long as the most talented in the community don't leave the Windows platform, it could lead to a more vibrant and productive Windows developer community.
Unfortunately, its been my experience that the Windows developer community rarely embraces anything outside of Microsoft. I hope your right though.