Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sure, it's one hour if you did that already 20 times and you know the ecosystem.

An hour is barely enough to go through the vimtutor which itself is pretty basic (aka you won't get far with it, so you need to keep learning and practicing).

If you are a vim newbie, it takes a lot of time to figure out you need plugins, then figure out how to install plugins, then what's the difference between plugin installers, finding the needed plugins for your languages, getting familiar with each plugins commands, resolve any conflicts between them, then you need file pickers, debuggers, task launchers, snippets, split screens, multi tabs, etc... Even then, you only made things work once... Good luck figuring that out in one hour...

Then you'll need to keep the config working, practice and memorize the commands, movements, and maybe customize your workflow.

Configuring vim to replace your IDE may be worth it, but "set it up in one hour" is, in my experience, extremely unrealistic.



I think it takes at least one month to get into vim, let alone mastering any of the plugins, and afterwards you keep learning every day.

IMO this is not due to the difficulty of installing plugins (which is becoming easier and easier), but rather to embrace the vim "philosophy".

Many think that VSCode is better because easier to use and has more features. However I think this is because they don't use any advanced features of VSCode either, only the glaring obvious ones.


I am not talking about learning vim. Of course, that is a huge time investment and you have to make your own judgement if that is worth it (for me it absolutely was, but I was in University with few obligations and lots of time).

I am talking purely about going from a vim without IDE-like tooling to one including it. That can be done in an hour.


Still, IMO it can only be done in an hour if you've done it already... You need more time than that for finding the plugin candidates, evaluating them, installing the right plugins, then you need a test run where you lookup the key bindings, on vim it's not as easy to discover features as in a "GUI" IDE.


>on vim it's not as easy to discover features as in a "GUI" IDE.

Unless you find the correct plugin :-)


> If you are a vim newbie, it takes a lot of time to figure out...

The horror!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: