> It took me 4 months to know enough of Vim and be comfortable enough to ditch my previous editor for good.
OK, but you can be productive with Eclipse or Jetbrains (or even Emacs) in an afternoon. This implies to me that they're easier.
For me, it also took a few months to get to the point where I felt comfortable getting rid of Emacs and use Vim for everything, but it only took me a few days to be productive with Emacs initially. The swap was worth it, but it was a steep learning curve.
Eclipse and friends are more approachable than Vim because they all follow the same familiar model. With so much of the core in common, newcomers and switchers have very little to learn to use those tools efficiently.
Vim being a modal editor, it is very unfamiliar to newcomers and switchers so they have a lot more to learn to use it efficiently.
But "little to learn" doesn't necessarily mean "easy to learn" and "a lot to learn" doesn't necessarily mean "hard to learn". In practice, "little to learn" means "easy to pick up" and "a lot to learn" means "hard to pick up", which is something else entirely. Eclipse, IntelliJ, VS Code, etc. are definitely easier to pick up than Vim but that doesn't make Vim "hard to learn" at all. It just means that, if you want to get something done quickly or don't want to invest too much effort into it, Vim might not be the most appropriate tool in the toolbox.
Take Sublime Text, for example. It followed a familiar editing model but its documentation was so lacking that members of the community had to put up an alternative doc. ST was (I have no idea how it fares today) definitely "easy to pick up" but also "hard to learn", all because of poor documentation.
Obviously, the modes, the wonky ways to copy and paste, etc. have always made Vim "hard to pick up". But with vimtutor as a first step and the very well written and progressive user manual as a second step, it _actually_ is "easy to learn". There is literally no obstacle beside one's own laziness or lack of focus or something external out of one's control. You _really_ move from super basic stuff, to less basic stuff, to cool stuff, to mind-blowing stuff in the most gentle, step-by-step way. The user manual is awesome.
In short, Vim is easy to learn and it has a very smooth learning curve.
The things people have trouble with are:
- the off-putting unfamiliarity of the first contact,
- the lack of menus and things that would make it easier to pick up,
- the unfounded expectations, reinforced by social media bullshit,
- the unfounded fears, reinforced by social media bullshit,
- the perceived need to be productive right now,
- a general taste for battery-included things,
- a general confusion between "learning about something" and "learning something",
- a general aversion for learning and, mostly, being taught,
- and for reading,
- the false impression of being smart enough to get it without learning,
- a goal-oriented approach that seems to justify every fucking shortcut ("I'm a React Dev, give me a config, plz."),
One reason I chose Vim is because I was tired of reaching the limitations in various editors I've tried and I wanted one I wouldn't outgrow.
It's been about 10 years and I'm still learning new things, even though I've had the basics down for quite a while. There have been times I've gone down some deep Vim rabbit holes for a particular project; it's great knowing all of the power is there any time you need it.
OK, but you can be productive with Eclipse or Jetbrains (or even Emacs) in an afternoon. This implies to me that they're easier.
For me, it also took a few months to get to the point where I felt comfortable getting rid of Emacs and use Vim for everything, but it only took me a few days to be productive with Emacs initially. The swap was worth it, but it was a steep learning curve.