![]() I learned how to drive a car in an automatic, I learned how to use a stick shift in a manual car. They're bolted onto a bike and then removed when they're no longer necessary. Training wheels aren't a prerequisite for learning to ride a bike and they're not typically separate thing from a bike. I could change vim to use CUA commands, be mouse-focused, and default to insert mode and I'd still be using vim. Kind of their prerogative and one of the nice things about extensible programs like vim is that people can do exactly that. > they try to replicate their previous ready-made config anyway. Pretty much all the typical vim paradigms are exactly the same. There is a list of different keybinds from vanilla vim in their documentation and you can disable them with one line in your config. You being weirdly gatekeepy about this doesn't change the fact that they're using the same application that you are, except they loaded a config different from yours. ![]() > they get very frustrated by the real Vim In fact I think in quite a lot of cases it's way worse. Can people make this approach work? Sure, but that doesn't mean it's better. Training wheels on a bike exist for the same reason too. They typically don't start students off learning to write Assembly even if their intent is to be an Assembly programmer. ![]() The same can be said for something like walking and then running, or learning how to program. So no, I wasn't better off learning it directly. This resulted in a much easier time for both me and the clutch. I gained confidence on the road and then I went back to learning how to drive stick. I switched to learning on my mother's car, which was an automatic. I skipped gears, Started from a stop in 3rd gear, and had a whole lot of frustration trying to deal with both the concepts of driving the car, the rules of the road, and trying not to completely destroy the clutch of the car. I remember when I learned to drive my father started me on his car with a manual transmission. This is not really the universal truth that you think it is. > Someone interested in $THING would be better off learning $THING directly rather than tip-toeing around it. They can, after all, switch to building out their own config down the line if they feel the need or desire to. I think for someone that is interested in using Vim (or Emacs, for that matter), these premade configurations with their own superset of paradigms seems like a much better approach to going about it. That isn't even mentioning the fact that it all hypothetically just works together and you can be productive actually programming out of the box with something like this. Something like SpaceVim kind of makes it so someone doesn't have to concern themselves with that because someone designed the entire thing from the ground up so you're less likely to run into issues that someone who's gradually built up their vim config over time would. The end result is kind of a sort of functional stack but without much consistency since it's evolved over time and I simply don't want to refactor it into something more sensible with less conflicts. I have my own configuration for vim/neovim, but there's a lot of faffing about finding plugins and tweaking settings to suit my workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |