Re:Your problem with Vim is that you don't grok vi
by mayanksinghal on Monday August 22, 2011 @07:25PM
(#2914599)
In a dumb Editor:
On an intelligent IDE:
I still want to learn Vim, because I somehow find it 'artistic'. There is some inherent beauty in Vi that I would love to be a part of. Unfortunately, the learning curve is fairly steep and the fear of losing productivity for 2 weeks is too huge. I still use vi for small changes, but for coding I find eclipse a more useful tool.
[ Parent
| on HN ]
Re:Your problem with Vim is that you don't grok vi
by sirclueless on Tuesday August 23, 2011 @02:18AM
(#2915578)
There's another giant advantage to renaming in an IDE over a text editor: You can be sure not to clobber any other variable/method references.
Here's an example, I want to change the name of my MyClass.Execute() method to something more descriptive. In an IDE, I right click and rename and I'm done.
In vim or other plaintext editors this is practically impossible without manually inspecting each call-site. Is "foo.Execute()" a reference to MyClass.Execute() or YourOtherClass.Execute()? Without actually parsing the program it's tough to know.
I love using vim, and I'm getting better at it the more I use it, but this is one of the major productivity drains I encounter that an IDE does way better.
Re:Your problem with Vim is that you don't grok vi
by Ideka on Monday August 22, 2011 @08:17PM
(#2914748)
You forgot to take the conversion rate between clicks and keystrokes into account.
c = (k.d.t.r) / 13333337
Where:
c = click
k = keystroke
d = distance in centimeters between the "J" key and mouse
t = area to be clicked in pixels²
r = screen resolution in pixels²
Re:Your problem with Vim is that you don't grok vi
by mayanksinghal on Sunday August 28, 2011 @05:14PM
(#2934990)
There are no clicks, the Right Click Key on keyboard is just too awesome! :)