Slashdot Mirror


Does Visual Studio Rot the Brain?

duffbeer703 writes "As a UNIX guy dragged kicking and screaming into the Windows world, I've never really been able to enjoy Windows programming. Charles Petzold, who is a long-time developer for DOS & Windows really laid out the reasons for me at the NYC .NET Dev group. Visual Studio and Microsoft tools force you to adopt programming techniques designed around implementation speed, not understanding or quality."

6 of 790 comments (clear)

  1. Re:Force? by abscondment · · Score: 0, Troll

    I've been forced to restart a visual studio crash more than twice a day this week. I'd much prefer if they merely allowed me to crash it, when I felt like it.

    I can't wait until I return to my normal job, programming in a real IDE that doesn't freeze so often.

  2. It must be Microsoft's fault! by Jeian · · Score: 0, Troll
    This is just silly. How on earth does a software program *force* you into bad programming techniques? Either you know how to do it right, or you don't.

    But any excuse to bash Microsoft, eh?

  3. Re:yes, it does rot your brain, or at least habits by CyricZ · · Score: 0, Troll

    Let it cultivate. That approach will only go so far. Once applications become moderately complex, that whole methodology of programming collapses. Frankly, I wouldn't mind if it took with it the people who fell for it. They probably shouldn't be working as programmers anyways.

    --
    Cyric Zndovzny at your service.
  4. Deep Thoughts with Jack Handy by cnerd2025 · · Score: 0, Troll

    Does Visual Studio Rot the Brain?

    Is M$ a monopoly?

    if (USER_OS == "Microsoft")
    {
    printf("Your brain is being rotted!!!\n");
    }

  5. Much Shorter Answer: by LFS.Morpheus · · Score: 0, Troll

    Yes.

    (If you decide to RTFA, be prepared to set aside an hour.)

    --
    The space unintentionally left unblank.
  6. Strange... by ninja_assault_kitten · · Score: 0, Troll

    My experience was exactly the opposite. Until maybe 2 years I had never even attempted to write an application in or for Windows. VI was my lord and C/Perl/Python my New Testiment then one day after feeling somewhat deflated with what my GTK apps were looking like based on the effort put into them, I decided to venture into the world of Visual Studio just for a taste. The results were not what I expected...

    After a few short days of using Visual Studio I really started to come out of my shell. While I had used IDEs like Visual Age before, they never really appealed to me, VIM was about as close as I felt I'd ever get to a GUI IDE. Now all that had changed. Visual Studio just made it easier to focus on what I was here to do, write an application. I was simply more efficient and I took it upon myself to attempt a somewhat large project to really get my hands dirty.

    I decided to port a large distributed network analysis application I had written for FreeBSD using a combination of Perl, C and PHP in C# using ASP.NET, Windows Services and some WinForms. This project had taken me approximately 1.5 years to complete on the UNIX side of the house and I was planning on re-writing every line of code for Windows. Quite simply, what took me 1.5 years to write in UNIX with VIM, took me a little over 6 months with Visual Studio and the help of .NET. But things didn't stop there. Not only was the application dramatically enhanced, but it was much more scalable and robust.

    Don't get me wrong, I still code in VI and most of my client/server apps have Linux/FreeBSD support, but my IDE of choice is definitely Visual Studio. No question.