Great insights, articsputnik. My journey with Vim began in a similar way. Initially, I was overwhelmed by the "Vim way" of doing things, but over time, the rationale behind its design choices began to make sense.
The idea that you're editing text more than you're writing it is profound. And as you rightly pointed out, the Vim language makes so much sense once you grasp its fundamental grammar. It's not just about memorizing commands, it's about understanding the logic and structure behind them, and then combining them in intuitive ways.
Regarding Neovim, I've been hearing a lot about it, especially in the context of Lua configurations and extensions. Do you think it's worth the switch for someone who's deeply invested in Vim? Or should they only consider it if they're looking to write plugins or heavily customize their setup?
Lastly, I agree wholeheartedly with your advice on when not to learn Vim. It's not for everyone, and there's no shame in that. Some people are perfectly content with other editors, and that's okay. But for those who are willing to climb that steep learning curve, the rewards are immense.
The idea that you're editing text more than you're writing it is profound. And as you rightly pointed out, the Vim language makes so much sense once you grasp its fundamental grammar. It's not just about memorizing commands, it's about understanding the logic and structure behind them, and then combining them in intuitive ways.
Regarding Neovim, I've been hearing a lot about it, especially in the context of Lua configurations and extensions. Do you think it's worth the switch for someone who's deeply invested in Vim? Or should they only consider it if they're looking to write plugins or heavily customize their setup?
Lastly, I agree wholeheartedly with your advice on when not to learn Vim. It's not for everyone, and there's no shame in that. Some people are perfectly content with other editors, and that's okay. But for those who are willing to climb that steep learning curve, the rewards are immense.