4 ms·

The real power of vim is its proven staying power. It is worth the investment to learn it. It's been around for a long time and is likely to be around for much

The real power of vim is its proven staying power. It is worth the investment to learn it. It's been around for a long time and is likely to be around for much longer. Newer, hip editors that depend on one person or small company to make a living maintaining their product cannot provide such assurances. Some have suggested open sourcing the application, but I am not sure that has worked for Text-Mate 2. Vim has been around, will be around, and is available pretty much every where and has a giant community. That's the point.

zalew 14y ago
you can replace vim with eclipse and all you said still stands valid.
- ajanuary 14y ago
  To add some figures: * vi is 36 years old, vim is 21 years old * Eclipse is 12 years old vim is on pretty much every linux box. Eclipse isn't.
  - mercurial 14y ago
    But it should be! Imagine how productive you would be with an edipsesudo instead of visudo :)
  - Evbn 14y ago
    How many Linux boxes do you spend >10hrs coding on in a year?
  - zalew 14y ago
    it is on mine and it's all that counts. unless what you mean is that it doesn't work without an X session on remote hosts, but in general I don't work on live code. 'The real power of vim is its proven staying power' is a non-argument, today I work on stuff that didn't even exist 10 years ago, there is no guarantee vim will be even usable for the sort of work you will be doing in a decade, and for sure there is no guarantee it will be the best choice. both vim and eclipse are here to stay for the next years and both have a lot of support. there are lots of reasons to learn/use vim, but a 10 years longer historical consistency isn't one.
- btipling 14y ago
  It's probably worth getting familiar with Eclipse, but it wont be on your ubuntu-server when you ssh into it.
  - zalew 14y ago
    I know, see my other comment in this tree. we are getting a bit off track with this, but since we are here, what is it with the arguments about editing live code on a server? source control + continuous integration + configuration management = never again touching live code on the server (unless in serious panic mode). editing code on an ssh session is not how I imagine my desired workflow to look like, to be honest I wish anyone doesn't have to do that. btw, I know vim is amazing. I'm arguing the arguments, not the case.
    - btipling 14y ago
      you probably shouldn't, but if you needed to, it would be there for you

zalew 14y ago

you can replace vim with eclipse and all you said still stands valid.

ajanuary 14y ago
To add some figures: * vi is 36 years old, vim is 21 years old * Eclipse is 12 years old vim is on pretty much every linux box. Eclipse isn't.
- mercurial 14y ago
  But it should be! Imagine how productive you would be with an edipsesudo instead of visudo :)
- Evbn 14y ago
  How many Linux boxes do you spend >10hrs coding on in a year?
- zalew 14y ago
  it is on mine and it's all that counts. unless what you mean is that it doesn't work without an X session on remote hosts, but in general I don't work on live code. 'The real power of vim is its proven staying power' is a non-argument, today I work on stuff that didn't even exist 10 years ago, there is no guarantee vim will be even usable for the sort of work you will be doing in a decade, and for sure there is no guarantee it will be the best choice. both vim and eclipse are here to stay for the next years and both have a lot of support. there are lots of reasons to learn/use vim, but a 10 years longer historical consistency isn't one.
btipling 14y ago
It's probably worth getting familiar with Eclipse, but it wont be on your ubuntu-server when you ssh into it.
- zalew 14y ago
  I know, see my other comment in this tree. we are getting a bit off track with this, but since we are here, what is it with the arguments about editing live code on a server? source control + continuous integration + configuration management = never again touching live code on the server (unless in serious panic mode). editing code on an ssh session is not how I imagine my desired workflow to look like, to be honest I wish anyone doesn't have to do that. btw, I know vim is amazing. I'm arguing the arguments, not the case.
  - btipling 14y ago
    you probably shouldn't, but if you needed to, it would be there for you