VS takes ~way~ to long to parse lines of code, or load header (for it's auto-completion), and has serious issues with updating/timestamping resources durring a build (I think I had v2004 or something though).
really odd that you say that. wednesday I was trying to diagnose a problem we were having at work. we have a query that takes about 5 hours to run, returns some 3-400 thousand records that are sent via xml (for each record) 200 records at a time to a solr search engine. well, when the update completed, instead of having the complete set of data it would have about 200 less records than it should have. so to find the problem, I logged every record sent to the search engine to a file. that file ended up in the realm of about 12 gig. I physically could not open it in any other editor. I could view it w/ head / tail and more, but anything else bombed. oddly enough, it loaded right up (seconds) into visual studio and I was able to scroll up and down the file as if it were 12k... so I'm perplexed as to how anything smaller than a 12 gig log file would take an editor so long to load.
as for the time it takes for loading autocompletion, that again has me wondering.
my typical week consists of working on SOLR (my least favorite part of the job. it runs on linux, and I use vi to update its java code base as the server doesnt have X11 installed so I cant use a GUI editor), an update windows service that post data to that server, which is written in .NET. and use eclipse for other random things we do. not a week goes by that I'm not using one of these different editors, and given the consistency in working w/ the different variety of editors, I can get a lot more done in eclipse and visual studio than anyone could in vi, simply because so much of the code is generated with the editor, if its not generated, its typed out for me as I code w/ the intellisense / code completion.
anyone who'd prefer vi over visual studio or eclipse either 1. cant afford good development software, 2. cant afford a decent computer made in the last 5 years 3. has a lot of time to kill, 4. still programs in cobol, 5. is out of a job, or 6. is locked away in a mental institution and does programming for therapy.
Plus the overhead of 3 blue screen a week... and windows...
sounds like somethings not configured right. if you're getting 3 blue screens a week, anything could seem like it takes forever to load, and might seem unstable.
I dont do any php professionally (the idiots I work with thing C# is the end all of programming languages and would rather develop web apps in that bloated crappy web technology than a fast clean php) but I like zend studio at home. then again I have a super computer at home so there isnt anything on the market that could slow this thing down (even swing or SWT).