Another predator preying on newbies.
Don't waste your money on this. Doing $ vimtutor and then going through the user manual is all it takes to learn Vim. Easy, free, and built-in.
Don't waste your money on this. Doing $ vimtutor and then going through the user manual is all it takes to learn Vim. Easy, free, and built-in.
Lots of books are written about things people are anxious about or afraid of in the sole purpose of banking on those anxieties and fears.
Step 1: convince vim-curious people that a) it will turn them into elite hackers and b) that it is freaking hard to learn.
Step 2: capitalize on the tension created at step 1 by providing them ways to skip b on the way to (imaginary) a.
Aside: To any newbies that want to read the PDF or Epub version and it's no longer free on Gumroad, hit me up and I'll send you a copy.
Neither the licence of that thing nor its price tag have anything to do with it.
And they provide a link [1] to free Vim resources available online, on a page that the author maintains themselves.
This is the opposite of what someone "preying on newbies" would do.
[1] https://learnbyexample.github.io/curated_resources/vim.html
I mean, taking this logic to its extreme, should universities by completely abolished, since most of the information available in universities is also available online for free?
That would be a different logic.
Maybe you're some hypergenius who picked up Vim in an afternoon, but I know several people who I recommended "just go through Vimtutor" and it didn't stick for them.
> Modal editing never really took off, so people's exposure to text editing prior to learning Vim is generally something like MSOffice, which is not modal.
Well, modal editing is just some $NEW_THING you must learn to do $ACTIVITY efficiently. Just like a new framework or ice skating. Not having been exposed to it prior to your first time is not a handicap because no one has. Every budding vimmer is literally equal before modal editing.
> Maybe you're some hypergenius who picked up Vim in an afternoon
It took me 4 months to know enough of Vim and be comfortable enough to ditch my previous editor for good.
> but I know several people who I recommended "just go through Vimtutor" and it didn't stick for them.
Well, that's a dumb advice so no surprise, here: you rigged them for failure and they failed. vimtutor only covers the basics needed for adding a line to /etc/hosts or write a commit message so no wonder why they bailed out if they believed they were going to be wizards after a 30 minutes tutorial. The real learning starts at :help user-manual.
Besides, giving up after vimtutor is perfectly OK. Vim is just one editor among many and it is not for everyone.
Learning Vim is _not_ hard. What _is_ hard is using it efficiently without learning it, which makes people take all kinds of silly shortcuts and spread all kinds of silly ideas.
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.
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."),
- etc.
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.
It's simply not the case. Maybe it was the case for you. Maybe you purchased a vim book and didn't become this mythical hacker wizard. maybe vim seems absurdly simple to you because you are a genius. I don't know!
But I do know this - other people have different contexts, different knowledge, different experiences than you do. When you stomp around angrily and arrogantly denouncing a perfectly innocent thing like a vim tutorial, and show zero indication that you understand that other people find things valuable when you cannot see that value... it just makes you look like a fool.
I'd put my money on the notion that very few, if any readers of HN are going to be impressed by your furious denouncement here - rather they are only going to see a weak fool shaking his tiny fists at a perceived slight for no special reason. Maybe they'll chuckle. Put me down for $20 on that action.
It's a hands-on tutorial. You don't "read it like a book", you follow it and do the exercises. Besides, only the internal links work, here, so there is no way to dig deeper from the comfort of your couch.
> Yes, it is certainly valuable to have it right there in the editor, easy to consult at a moment's notice.
No. The user manual is not something you "consult at a moment's notice". It's something you focus on, deliberately, during 1-2 hours sittings.
Well, I have been known to take helpfiles like this and "read them like a book," or at least like a reference manual to a particular group of functions.
> Besides, only the internal links work, here, so there is no way to dig deeper from the comfort of your couch.
Internal links are exactly what I'm looking for, so I can jump from one part of the file to another, but external links in the PDF file work just fine.
> No. The user manual is not something you "consult at a moment's notice". It's something you focus on, deliberately, during 1-2 hours sittings.
Yes. I have consulted user manuals at a moment's notice.
There doesn't seem to be much intersection between my life experience and yours.