Earlier quoted context omitted.
I really don't think the ASP.NET MVC can be classified as a black sheep. Neither are things like Linq or Entity Framework. Microsoft is still doing a lot of the interesting stuff in-house.
MVC was developed skunk works style, as was Linq. And MS has only begun embracing MVC anywhere near fully lately. Meanwhile, Linq has been effectively abandoned in preference to the bloated entity framework. If Microsoft had their heads screwed on straight MVC would be the default ASP.NET web-site project type in Visual Studio and Linq would have gotten the love it deserved, even if it competed with EF. I fear that w…
Phil Haack quit Microsoft for GitHub
71–80 of 127 posts
Re: Phil Haack quit Microsoft for GitHub
#72When I went looking for a git win32 binaries a while ago the attitude was basically "lolz get a mac/linux box". Which is why I use hg instead of git. It's great to see an open source community, that isn't engulfed in the sanfrancisco linux/mac mono culture bubble, reaching out to Win developers for the benfit of everyone.
From the cmd.exe prompt, some of them are still working, as long as the cygwin bin folder is in the PATH variable, and the executables end with .exe, and are not cygwin symlinks (the file would be very small and contain something like !) - then they won't execute, but you can still execute them from cmd.exe, like this:
sh -c "gitk --all"
Hopefully git is still normal executable (gcc is not, for that: sh -c "gcc --help"
C:> gcc --help
Access is denied.
C:> sh -c "gcc --help"
... Help displayed
Re: Phil Haack quit Microsoft for GitHub
#73Re: Phil Haack quit Microsoft for GitHub
#74Earlier quoted context omitted.
Disagree. It's gotten better, but the tooling is awkward, the commonly used UI (TortoiseGit) is wonky, and not being a "native citizen" on the OS isn't acceptable--MSYS is a mess to have around on a Windows machine and even the "minimal subset" that you can install with Git is more than I consider acceptable. (I realize that entirely too much of Git is UNIX-based plumbing, but that's their problem.) I gave Git anothe…
git GUIs on windows are all pretty weak, but the git command line and git bash work perfectly well. my experience with git GUIs in general (regardless of the OS) is that you should just give up and use the CLI.
Re: Phil Haack quit Microsoft for GitHub
#75I really hope this leads to better Git tools for Windows developers. I've attempted to host several C# projects on GitHub in the past, but I always end up giving up and using either CodePlex or BitBucket because it's so much easier to get up and running with HG and SVN. Edit: Git tools, not GitHub tools.
Re: Phil Haack quit Microsoft for GitHub
#76Earlier quoted context omitted.
Disagree. It's gotten better, but the tooling is awkward, the commonly used UI (TortoiseGit) is wonky, and not being a "native citizen" on the OS isn't acceptable--MSYS is a mess to have around on a Windows machine and even the "minimal subset" that you can install with Git is more than I consider acceptable. (I realize that entirely too much of Git is UNIX-based plumbing, but that's their problem.) I gave Git anothe…
git GUIs on windows are all pretty weak, but the git command line and git bash work perfectly well. my experience with git GUIs in general (regardless of the OS) is that you should just give up and use the CLI.
I always thought it was cool that Mercurial is written in Python, part of that cross platform magic.
Re: Phil Haack quit Microsoft for GitHub
#77Earlier quoted context omitted.
I really don't think the ASP.NET MVC can be classified as a black sheep. Neither are things like Linq or Entity Framework. Microsoft is still doing a lot of the interesting stuff in-house.
MVC was developed skunk works style, as was Linq. And MS has only begun embracing MVC anywhere near fully lately. Meanwhile, Linq has been effectively abandoned in preference to the bloated entity framework. If Microsoft had their heads screwed on straight MVC would be the default ASP.NET web-site project type in Visual Studio and Linq would have gotten the love it deserved, even if it competed with EF. I fear that w…
Also, FWIW, a lot of Microsoft's biggest public facing sites run on ASP.NET MVC now, so even if you assumed a lot of stupidity or evilness, there's a lot of inertia behind ASP.NET MVC.
Re: Phil Haack quit Microsoft for GitHub
#78For 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
Github is my social network. I wake up into it, i follow it, push to it during the day, and I survey it before sleep. I love Github (in fact i'm inlove with Github). I depend on Github. I don't do facebook, g+ or twitter for socializing. I used to admire Haack aswell. He's a great guy. However I fell out of love with .net. I am a polyglot programmer, with strong background in .net. To understand these Haack's "accomp…
And then maybe this whole us versus them thing will stop.
There is nothing genious about MVC3
As a Python developer, I don't think there's anything genius about Ruby on Rails either. It's just a bunch of borrowed features that were added with good taste + marketing + community enhancements. Overall the whole package is great, but it does stand on the shoulders of giants nonetheless. Borrowing stuff is not a sin - if anything I blame Microsoft for the often displayed NIH syndrome.Re: Phil Haack quit Microsoft for GitHub
#79Earlier quoted context omitted.
MVC was developed skunk works style, as was Linq. And MS has only begun embracing MVC anywhere near fully lately. Meanwhile, Linq has been effectively abandoned in preference to the bloated entity framework. If Microsoft had their heads screwed on straight MVC would be the default ASP.NET web-site project type in Visual Studio and Linq would have gotten the love it deserved, even if it competed with EF. I fear that w…
Note: I never used linq-to-sql, but in my experience EF (especially with the code-first stuff) is a decent, lightweight, and highly usable.
Re: Phil Haack quit Microsoft for GitHub
#80Perhaps he'll work on a whole bunch of non-Microsoft stacks now? Getting Open Source within Microsoft and the Microsoft communities is probably more an issue with culture rather than tooling - a hire won't 'fix' that. It would take many counter-culture things (and years) to change I think. Phil working at Github rather than wanting to work at Microsoft is the interesting aspect, and I can't see why that would be 'good' for Microsoft.
Congrats to Phil and Github!