Understanding the Origins and the Evolution of Vi and Vim
1–10 of 128 posts
Re: Understanding the Origins and the Evolution of Vi and Vim
#2Re: Understanding the Origins and the Evolution of Vi and Vim
#3Re: Understanding the Origins and the Evolution of Vi and Vim
#4Re: Understanding the Origins and the Evolution of Vi and Vim
#5Re: Understanding the Origins and the Evolution of Vi and Vim
#6I love my Jetbrains IDEs, but you can take my Vim plugin from my cold dead hands :)
Re: Understanding the Origins and the Evolution of Vi and Vim
#7It's incredible how good of a design Vi is. Try this experiment: Busybox includes a tiny clone of vi with a reduced feature set. It's very stripped down when compared to Vim or even other vi clones, but as a pure text editor it's still more powerful than most modern day IDEs . I love my Jetbrains IDEs, but you can take my Vim plugin from my cold dead hands :)
Re: Understanding the Origins and the Evolution of Vi and Vim
#8I was slightly surprised that they didn't add a mention of neovim.
Re: Understanding the Origins and the Evolution of Vi and Vim
#9Re: Understanding the Origins and the Evolution of Vi and Vim
#10I was slightly surprised that they didn't add a mention of neovim.
while neovim is great and I intend to switch even, some time down the road, it caused a not-really-compatible fork and diverted the efforts, I wish them to be merged however hard it will be.
I will make a random comparison to latex vs typst (typesetting software). Both incorporate a programming environment, you can write a program right in your document. The difference is that the tex programming environment is a bit unapproachable and not very similar to other languages you may already know, while typst's equivalent is consistent and more similar to languages you know.