Over the past year, an "ALT.NET movement" has sprung up. They have a wiki meetings. When it started out, it sounded like a good idea.
For those that aren't hip (read: not on twitter), ALT.NET has been a lightning rod in the community. The simple idea was "Alternatives in .NET" (not to .NET as one might assume from the name) - using the best tool for the job, wether it came from Microsoft or not. That means if NUnit was a better testing tool than MSUnit, ALT.NET would encourage NUnit.
A nice ideal, but in reality one man's "best" is another man's steaming pile of dung. Seriously, if developers could agree on the "best" of anything we wouldn't have 78 (by my last count) different tools all aimed at mapping a database to objects. So in practice, ALT.NET got into the name-calling, ego-bashing, and flame wars Internet forums do so well at. I still like the idea though, and didn't mind following along the ALT.NET crowd... that is until they started going to extremes.
I like meat (stay with me here). I recognize that McDonald's may not be the best quality meat, and may even be harmful to me. I'm interested in hearing about alternatives to McDonald's - but when talking to someone about this, the terms "vegetarian" and "vegan" come up. The logic seems to be because I agree McDonald's meat is bad, I must leave all meat.
Another example; when I was young I read C.S. Lewis' Mere Christianity. He argued there is a God because we all share a common view of morality, and that this was something we knew and didn't need to be taught. I dug this, it made sense to me, so I agreed. The he argued that since we agreed on this God fellow, and Jesus was his son, we believe in his existence too.
Both of the cases show a "logic leap" in which we went from point A to point C and I don't recall stopping for lunch at point B during the trip. ALT.NET just arrived at point C for me with David Laribee's latest post on tools.
In the post, he makes the case for the "Developer Vegan" or what I'll now call "Degan" to drop back to the command line as the ultimate in process mastery. Now, there have been rants against the IDE before and while I do agree there are dangers and problems in using the IDE, I strongly disagree the answer is to toss the IDE aside.
I'm going to make this simple - Time is Money - a tool that saves time is better than a tool that costs time. If I can product an application in less total time (total time being time to launch and support) with Visual Studio than Vi, Visual Studio is the better tool. As a manager, if I train new hires in less time on Visual Studio than Vi, Visual Studio is the better tool. If my build process is "right click, select build" I save time by not having to train every developer on the build system, nor waste time configuring each workstation to be able to build the project.
Rather than attempt to ignore the reality of time and money, I would like to see suggestions and improvements made to the IDE. Address the weak points - if NUint is going to save time once setup, then ease the setup and integration - VS2008 supports a very flexible framework for plugins and extensions. Just because your audience is other developers does not allow you to exempt yourself from Agile goals and providing a solid user experience.
Bottom line, if ALT.NET is heading down this Degan path it is dooming itself to obscurity.
PS. I really dig vi, and have it on all my machines - I just don't require other developers use vi in order to work on my code.
