I am either misunderstanding your post or you might be misunderstanding mine.
Vim is not the command line. It can be used in a command line, which is a nice feature, but I use Vim because it makes editting text a far smoother and more reliable experience than most text editting GUIs have provided.
I also would not say command line is superior to GUI. Both have their trade offs, and like you said, use the tool that works best for you.
As a developer though, I do fully believe devs should be taught how to use command line, and I believe they should be taught how to use Vim. Command line is near mandatory, because sometimes you cannot easily do something using a GUI, especially if that GUI is just buttons that run command line prompts like a lot of Git tools are. Solving Git issues without using command line frankly feels like a horrid scenario because you dont have the finer level of control required to unfuck yourself out of a Git issue.
Vim should be taught because it improves navigation and editting of text in much more efficient and faster ways than a GUI generally can. This is very useful in development, as editting code is often a bit tedious with a mouse and common keyboard shortcuts, and not needing to take your hands off your keyboard really lends itself to keeping focused on your code. It improves productivity while also being a useful skill to learn, as a lot of apps support Vim bindings that don’t necessarily involve code, such as Obsidian.
For other keyboard based professions, Vim would be useful but not mandatory.
If I misunderstood your post as bashing my post, then thats my bad. The way I read it felt like it was bashing my view of Vim by connecting it to the viewpoint of command line being better than GUI, which is not how I view Vim or command line at all.
deleted by creator
I am either misunderstanding your post or you might be misunderstanding mine.
Vim is not the command line. It can be used in a command line, which is a nice feature, but I use Vim because it makes editting text a far smoother and more reliable experience than most text editting GUIs have provided.
I also would not say command line is superior to GUI. Both have their trade offs, and like you said, use the tool that works best for you.
As a developer though, I do fully believe devs should be taught how to use command line, and I believe they should be taught how to use Vim. Command line is near mandatory, because sometimes you cannot easily do something using a GUI, especially if that GUI is just buttons that run command line prompts like a lot of Git tools are. Solving Git issues without using command line frankly feels like a horrid scenario because you dont have the finer level of control required to unfuck yourself out of a Git issue.
Vim should be taught because it improves navigation and editting of text in much more efficient and faster ways than a GUI generally can. This is very useful in development, as editting code is often a bit tedious with a mouse and common keyboard shortcuts, and not needing to take your hands off your keyboard really lends itself to keeping focused on your code. It improves productivity while also being a useful skill to learn, as a lot of apps support Vim bindings that don’t necessarily involve code, such as Obsidian.
For other keyboard based professions, Vim would be useful but not mandatory.
If I misunderstood your post as bashing my post, then thats my bad. The way I read it felt like it was bashing my view of Vim by connecting it to the viewpoint of command line being better than GUI, which is not how I view Vim or command line at all.