5 ms·
you can replace vim with eclipse and all you said still stands valid.
by zalew 14y ago
you can replace vim with eclipse and all you said still stands valid.
- ajanuary 14y agoTo 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 agoBut it should be! Imagine how productive you would be with an edipsesudo instead of visudo :)
- Evbn 14y agoHow many Linux boxes do you spend >10hrs coding on in a year?
- zalew 14y agoit 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 agoIt's probably worth getting familiar with Eclipse, but it wont be on your ubuntu-server when you ssh into it.
- zalew 14y agoI 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 agoyou probably shouldn't, but if you needed to, it would be there for you