![]() > 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. |