Earlier quoted context omitted.
I don't think it's constructive feedback in that it doesn't give anything for OP to do except just give up. johncoltrane gave the same feedback last time, so I don't see how this is supposed to be helpful to OP. [0] [0] https://news.ycombinator.com/item?id=31832423
OP is pretending falsely to help people "master Vim" via repetition. I'm using the same strategy to steer people toward better ways to learn Vim, without the lies. OP doesn't need help, it's the potential victims of that scam that do.
Show HN: I built an interactive course that helps you learn Vim faster
121–130 of 265 posts
Re: Show HN: I built an interactive course that helps you learn Vim faster
#122I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…
Re: Show HN: I built an interactive course that helps you learn Vim faster
#123I really want to like vim and I love some things about it, like the ability to move chunks about with only the keyboard. But so many things about it kill me. Like, why can't I hit right at the end of a line, and move to the next line? Who thinks that is a good idea? Also, why do I have to have a special mode to insert things? Having to change modes just seems so complex and unintuitive. And why does the help system n…
The modal nature of Vim is one of it's key features and makes a lot of sense. If you consider the keyboard the primary, if not singular, means of interaction, then there will be times you want to use the keyboard to type text and times you want to use the keyboard to control the editor behavior. In a "normal" editor, you have to use modifier keys to enter commands. In Vim, you do it by changing modes. It's actually quite powerful but you can't get past your own assumptions about efficiency.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#124I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…
Re: Show HN: I built an interactive course that helps you learn Vim faster
#125I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…
Vim is a text editor, not a code editor. IDEs are much more efficient for code edit.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#126I really want to like vim and I love some things about it, like the ability to move chunks about with only the keyboard. But so many things about it kill me. Like, why can't I hit right at the end of a line, and move to the next line? Who thinks that is a good idea? Also, why do I have to have a special mode to insert things? Having to change modes just seems so complex and unintuitive. And why does the help system n…
> an ordinary visual text editor Funnily enough, Vim is short for "Vi IMproved", and its predecessor vi is short for "visual"! --- Taking the time to learn Vim yields significant rewards if you're willing to meet it on its own terms. I certainly grant you that it's not for everyone. It's the agony and the ecstasy of deep tools. No pain, no gain. > The frustration is that probably there are fixes for all these things,…
set -o vi
And get vim in your bash shell. Then you wonder what the default mode is, and it turns out it’s emacs and you can do wild things like ctrl-A to go to the beginning of the line.
And now I cringe when ever I see someone painstakingly left-arrow for 30 seconds to edit something at the beginning of their bash prompt.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#127Earlier quoted context omitted.
I can't really understand whether you recommend Vim itself or not, because of these sentences: > Vim forces you to glue together lots of inefficient commands to manipulate text > Vim’s nasty bells and whistles you need to actually be efficient at manipulating text
I’m a power Vim user. I do not recommend it for code editing. Learn it as a curiosity if you want. It’s also handy for quickly editing over SSH. IDEs with multiple cursors are so much nicer than Vim.
Perhaps I'll stick with VS Code over SSH, then
Re: Show HN: I built an interactive course that helps you learn Vim faster
#128I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…
Okay, but you spend 2000 hours per year at work. So 10 hours on a config is only .5%, which is the productivity gain you need to realise to get that time back in one year (assuming you also spend 0 hours on fighting vscode). Unless you're retiring within the year, that calculus doesn't make sense. The productivity boost you get with from Emacs/vim is huge once you learn it well. I strongly believe that learning one o…
Re: Show HN: I built an interactive course that helps you learn Vim faster
#129Earlier quoted context omitted.
> why can't I hit right at the end of a line, and move to the next line? I know this is probably something that sounds like someone too far down the rabbit-hole to see where they came from, but I'm not sure why you'd want to do that. The horizontal movement is probably adjacent to the vertical movement on your keyboard. Just use the appropriate movement to get where you want to go? > Also, why do I have to have a spe…
My answer to all these things is that 90% of the time, I am not using a text editor. I will be writing in Word, or in LyX, or in RStudio, or in a text box. My muscle memory is used to that. You're absolutely right. You do sound far down the rabbit hole! I am used to being able to hold down the right key and traverse my entire document, as far as I like. Why would I want to stop at the end of a line? Any time I'm edit…
I mean chances are, if you're holding down a key in vim, you're doing an inefficient movement. That's kinda the point: it's a keyboard language that turns complex actions into compound, simple actions. If you're still using the simple movement and complaining about it not doing what you want, you're just not using vim correctly.
I'm not sure why people get this defensive, though. People like vim, people like editors-that-aren't-vim. Is that not okay? If you don't want to learn to use vim, this link isn't for you.
> but what if there were some kind of special key that could be pressed to issue controls?
This works for a limited number of shortcuts, and when you only want to issue a few. The point is that you can now issue a large number of "command" inputs, very quickly, without holding down a key.
> Again, you're right, I don't want to do anything new. Why would I? I want to get on with my job.
Then uh... don't use vim? Do you post on every "I wrote xyz course for abc language/tool/technology" expressing that you don't want to use it?
Re: Show HN: I built an interactive course that helps you learn Vim faster
#130My pet peeve is Vim tutorials that start with "use hjkl to move around" instead of "use `set mouse=a` to turn on the mouse." In my opinion you need to make sure that you are very clearly disclaiming that you are teaching a harder way of doing things in exchange for incredibly small productivity gains that will be realized years in the future, if ever. (This is basically a copy-paste of previous comments I’ve made, I…
I bet I could untrain with sufficient work but it's no longer worth it.