> Here's the thing, the best part about it vim is that it is not slow (plus paired with a terminal emulator like kitty/wez/alacritty). When I type the characters actually appear on the screen as I type them.
I just noticed that ~/.vimrc adds a small delay, even if it is empty. This is the test case:
Create a file with about 10 emtpy lines and type:
esc switch to normal mode
gg go to the top
ctrl + v, G select all lines
shift + i switch to insert mode
- line just type something
esc this will duplicate the first line until the end of the file
Having a ~/.vimrc, even if empty, sets 'nocompatible'.
Re:Vim After 15 Years
by andresgaitan on Thursday October 27, 2022 @05:41PM
(#33364411)
"When I type the characters actually appear on the screen as I type them"
Great quote. Perhaps one of the best arguments for using Vim
> I don't quite remember something and having the internal file history with a diff readily available.
You're already in a terminal, git is just one command away
> Some of the click and find implementation/usages never seems to quite there to me.
This really depends on the language you are working in, but generally vim's gd (and plugins that augment it) enough most of the time, otherwise grep/rg if you know what you are looking for. If you are using something really dynamic, e.g. ruby, then you're pretty much shit out of luck.
> I could go on, if you're truly being productive and not missing out on feature, more power to you.
Here's the thing, the best part about it vim is that it is not slow (plus paired with a terminal emulator like kitty/wez/alacritty). When I type the characters actually appear on the screen as I type them. With most IDE's (at least the ones I have used) there is a noticeable delay from when I have stopped typing and characters appearing on screen.
Another thing to add is that vim is very fast to start up and shut down, I open and close vim multiple times as I am working. With an IDE, startup times are atrocious and dont really fit my work style of cd'ing somewhere quickly editing something, cd'ing somewhere else and rinse and repeat.
In general I find the original command line tools to be much better than IDE provided equivalents or integrations, there's no unnecessary animations and much less cpu/ram usage. Though one exception for me is the database clients, where I much rather prefer a GUI than using the CLI client.
Your tests are already runnable from command line (assuming CI is setup).
Basically, Unix becomes your IDE