3 ms·

There are addons to make Visual Studio editing just like vim. Or Emacs if you prefer that.

Zak 16y ago
Most people don't use Emacs just for the editing, and a big part of the point of Vim is that it's a simple tool that does one thing and does it well. Almost any serious development environment (editor and development tools, integrated or not) can be made to do most of the stuff that any other can do. Tool preferences are about how the tool fits with the user's personal style, not specific checkboxes on a feature list, even if it's something like "customizability".
Daishiman 16y ago
And the Vim plugin is an absolute failure, and the development enviroment takes 30 seconds to startup, 30 seconds to connect to a TFS server over the Internet, and stutter every 20 seconds whenever you want to switch windows. oh, and let's not forget the 15 second build time for debugging. Vim is here, now, the very second you need it, over an SSH connection, and far, far more customizable and with more useful plugins. The advantages of Visual Studio (namely, integration of features and great code completion) are lost when a framework fits in your head and you've automated most of your tools. I say this as a person that spends 50% of his time on VS, the rest on Vim.
- Cymen 16y ago
  Are you using msbuild to build your project? I've figured that out and some of msdeploy so it seems like making the jump out of Visual Studio/Express should be straight forward (I came from Vim with PHP/Perl and often find Visual Studio/Express getting in the way more than it helps).
- kenjackson 16y ago
  First, VS shouldn't take 20s to switch windows. I just did it and it happened instantly. And I have 60 open windows (not including tool windows). Second, how is Vim more customizable than VS? I can't think of anything I can't do in VS. There's plenty I can't do in Vim. Vim does load faster. Although single file load with VS isn't too bad, but certainly no Vim. And don't use TFS... that's just bad mojo. I say this as a person who spent 12 years of his life using Vi/Vim before touching VS for the first time.
  - Daishiman 16y ago
    Have you tried using Silverlight for a RIA app? Rendering a XAML file takes at least 5 seconds, and it's a process that's riddled with bugs and consumes at least 1 gig of memory. I'm sure the WinForms designer is much faster (I've never had any trouble with it in VS 2008), but the new toolkits with WPF and XAML seem to consume all the resources of my dual-core laptop with 3 gigs or RAM (a somewhat acceptable dev machine), the parser is horrendous and prone to causing unexpected exceptions, and is generally not as nice.

Zak 16y ago

Most people don't use Emacs just for the editing, and a big part of the point of Vim is that it's a simple tool that does one thing and does it well. Almost any serious development environment (editor and development tools, integrated or not) can be made to do most of the stuff that any other can do. Tool preferences are about how the tool fits with the user's personal style, not specific checkboxes on a feature list, even if it's something like "customizability".

Daishiman 16y ago

And the Vim plugin is an absolute failure, and the development enviroment takes 30 seconds to startup, 30 seconds to connect to a TFS server over the Internet, and stutter every 20 seconds whenever you want to switch windows. oh, and let's not forget the 15 second build time for debugging. Vim is here, now, the very second you need it, over an SSH connection, and far, far more customizable and with more useful plugins. The advantages of Visual Studio (namely, integration of features and great code completion) are lost when a framework fits in your head and you've automated most of your tools. I say this as a person that spends 50% of his time on VS, the rest on Vim.

Cymen 16y ago
Are you using msbuild to build your project? I've figured that out and some of msdeploy so it seems like making the jump out of Visual Studio/Express should be straight forward (I came from Vim with PHP/Perl and often find Visual Studio/Express getting in the way more than it helps).
kenjackson 16y ago
First, VS shouldn't take 20s to switch windows. I just did it and it happened instantly. And I have 60 open windows (not including tool windows). Second, how is Vim more customizable than VS? I can't think of anything I can't do in VS. There's plenty I can't do in Vim. Vim does load faster. Although single file load with VS isn't too bad, but certainly no Vim. And don't use TFS... that's just bad mojo. I say this as a person who spent 12 years of his life using Vi/Vim before touching VS for the first time.
- Daishiman 16y ago
  Have you tried using Silverlight for a RIA app? Rendering a XAML file takes at least 5 seconds, and it's a process that's riddled with bugs and consumes at least 1 gig of memory. I'm sure the WinForms designer is much faster (I've never had any trouble with it in VS 2008), but the new toolkits with WPF and XAML seem to consume all the resources of my dual-core laptop with 3 gigs or RAM (a somewhat acceptable dev machine), the parser is horrendous and prone to causing unexpected exceptions, and is generally not as nice.