The things people build to avoid learning vi...
So first off I use Dvorak so I have to switch tons of the bindings so I can use reference layouts. My moonlander keyboard already gives me directional movement on home keys. I don't have a ton of things to automate that I cant do in Alfred and my keyboard has over 1000 possible slots for keys and macros, more than I could ever use. Unlike Alfred workflows, the macros are trapped in vim. I have to add a ton of plugins to get anything approaching the experience of Pycharm and now it's just as slow, the auto completion is worse, and it looks like ass. But hey at least I can use it over an ssh connection (gotta transport all of my config first!), as if sshfs is not a thing, not that my work load is all cloud containers so I rarely ssh at all anyways.
Micro fills a niche for me where I don't want to leave the terminal and just need to edit a few lines.
(Sorry, just joking, could not resist :P)
I use Vim (and Emacs) as a Dvorak user. I don't change the layouts; I just stick with mnemonics. e.g. in vim, g is "go..", c is "change..", d is "delete..". With Dvorak, the `jk` are adjacent, so that works out. `h` is still to the left of `l`... but, vim's keybindings are excellent at navigating in a line, so many `h`/`l` should be avoided anyway.
I think "hard to get vim to be as good a development environment as an IDE" is more/less a fair point.
Anyway, it's great that micro can fill a niche for you. I wish everyone could appreciate modal editing and symmetrical keyboards.
There is no reason in 2021 for to have such terrible discoverability. If it's such a great tool, why did no one see fit making it progressively learnable from within the tool itself?
I see people talking about using vim like some other talk about going to the gym. Great abs, fast editing, but... do you even code, bro?
Unless I'm working on trivial stuff, my crafting speed is rarely limited by my editing capabilities. When it is, it's usually because the code is repetitive and it's time to change it.
High-level language tooling like refactoring and static analysis are way, way more important for medium+ size projects productivity.These are much better served by an actual IDE than some one-off integration with an obtuse editor deriving macho pride from it's 1970's TTY-limited semantics.
vim comes with a tutorial that teaches all the basics from inside vim... It's installed pretty much everywhere, you just have to run vimtutor.
> I see people talking about using vim like some other talk about going to the gym. Great abs, fast editing, but... do you even code, bro?
Why the condescending tone?
Yes I do code, everyday and full time, and vim absolutely increased my focus and productivity.
There is way too much to talk about in a single post, but stuff like macros, showing multiple files at once, (tabs is not the natural way of doing things in vim), viewing multiple parts of the same file at once the native integration with the terminal (just ctrl-x to go back to the terminal and fg back to vim, or execute any command with :! ) are great for productivity when you have to deal with multiple tools.
> High-level language tooling like refactoring and static analysis are way, way more important for medium+ size projects productivity.
I agree, and that's why I use vim. I can do all of that more efficiently in vim because the refactoring tools are way more powerful, and everything is macro-able.
> These are much better served by an actual IDE than some one-off integration with an obtuse editor deriving macho pride from it's 1970's TTY-limited semantics.
Condescending and even insulting tone again... great.
FYI, vim has all the features of any modern IDE. The opposite is not true however.
> The things people build to avoid learning vi...
As if learning vi was the obvious thing everybody just needs to do. Which is a common attitude within certain circles. "It was hard for me, but I made it through and so should you, with just as much pain, haha".
I was brought into the world of computers with the promise that they would help build a better world, one where the edges of technology get softer as years pass.
vi insisting on menu-less text mode and rote memorization of arcane key combinations negates any progress that was made in the last forty years in software usability. I refuse vi because I believe there _has_ to be a better way of doing things.
I've already switched to this. Installing and configuring it was a lot easier than learning vi would have been.