3 ms·
People are always surprised when I mention that the Microsoft devs I worked with had free access to the highest tiers of Visual Studio, yet what they actually w
by prodigal_erik 12y ago
People are always surprised when I mention that the Microsoft devs I worked with had free access to the highest tiers of Visual Studio, yet what they actually worked in was vim and the internal fork of make. I don't know whether that's still true; it's been a decade now.
- wglb 12y agoWhen you say "Microsoft Devs", do you mean MS employees? If so I heard s similar tale back in the first days of .net, where most of the guys in one particular group were using emacs.
- wrs 12y agoWhen I was an MS dev (8 to 18 years ago), Visual Studio had nothing to do with "real work" on Windows systems programming. Quite a few people used a rather obscure editor called Source Insight (http://www.sourceinsight.com/ http://www.sourceinsight.com/) because of its code-navigation abilities, which were similar to an IDE's but worked on huge codebases that would take hours to actually parse and analyze "properly". Sort of a supercharged ctags.
- jmcphers 12y agoIt's still true (source: Microsoft engineer for 8 years, used vim and internal version of Unix tools). A lot of this has to do with the sheer size of many of Microsoft products' codebases. Visual Studio just can't handle projects with millions of lines of code, whereas vim + ctags elegantly handles the fragments of projects you build locally.