this post was submitted on 15 Feb 2026
63 points (89.9% liked)
Programming
25677 readers
193 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Many might disagree, but imo vim is the perfect text editor for a command line interface. It's just so simpel and does exactly what I need it to do without doing anything unnecessary
Vim has some pretty messy design... Starting at some of the action quirks and ending at vim9script
Never heard of vim9script, what is it. I must admit I don't use it for a lot of super complicated tasks just regular yaml and file editing. At for that it's perfect imo
Vim9-script is a bespoke DSL introduced in vim 9 which was to replace vimscript (the old config language) It was recieved as a bit wacky with its support for classes among other things.
neovim is a drop in replacement for vim that fixes the issues that bother me with vim
Might install that then in the future, if I remember it. Sudo apt-get install vim is just so ingrained in muscle memory
not sure why your getting downvoted
Nit: vim is a visual editor. It has a text interface, but it's not a command line interface.
An example of a command line text editor would be sed.
I know it isn't a cli but a text editor that you can use in a terminal, if there's any other difference i got wrong feel free to correct me