The State of Vim
lwn.net
lwn.net
I do try out neovim from time to time, but I don't care for Lua (vimscript is easier to read and less verbose for .vimrc), I don't need an LSP and I found treesitter often buggy and slow.
So I'm sticking with vim, here's to another few decades more, thank you to all maintainers!
I agree with you about treesitter too: it's not really better than the old regex way in terms of (non-)bugginess in my experience, and I've been hearing more and more reports of it being much slower than it's claimed to be.
TS is faster in other situations. for example with TS highlighting enabled entering "(" in the buffer is definitly faster in a julia file. (you can test this by holding down "(" in a .jl file and see the difference between TS enabled and only regex highlighting).
>>Yet the fire disasters that we’re seeing today are less wildland fires than urban fires, Cohen said. Shifting this understanding could lead to more effective prevention strategies.
>>“The assumption is continually made that it’s the big flames” that cause widespread community destruction, he said, “and yet the wildfire actually only initiates community ignitions largely with lofted burning embers.”
>>Experts attribute widespread devastation to wind-driven embers igniting spot fires two to three miles ahead of the established fire. Maps of the Eaton fire show seemingly random ignitions across Altadena.
>>“When you study the destruction in Pacific Palisades and Altadena, note what didn’t burn — unconsumed tree canopies adjacent to totally destroyed homes,” he said. “The sequence of destruction is commonly assumed to occur in some kind of organized spreading flame front — a tsunami of super-heated gases — but it doesn’t happen that way.
>>“In high-density development, scattered burning homes spread to their neighbors and so on. Ignitions downwind and across streets are typically from showers of burning embers from burning structures.”
>>This fundamental misunderstanding has likewise led to a misunderstanding of prevention. No longer is it a matter of preventing wildfires but instead preventing points of ignition within communities by employing “home-hardening” strategies — proper landscaping, fire-resistant siding — and enjoining neighbors in collective efforts such as brush clearing.
>>“If we think it’s wildfire, then we tend to maintain wildfire as the principal problem — with wildfire control as the solution,” Cohen said. “However, there is no evidence to suggest wildfire control is a reliable approach during the extreme wildfire conditions when community disasters occur.”
<https://news.ycombinator.com/item?id=37011324>
And yeah, that one hit really hard.
Not only in split mode, as you can also just switch between two buffers (or more) focused on different parts of the text.
What I normally do is kill the PID, and then open the file again and tell Vim to remove the lock file.
This can be automated. But even better would be to allow me to take over the session in case there were any unsaved changes.
- either adding to your `:help vimrc`
if has('clientserver') && empty(v:servername) try call remote_startserver('VIM-' . getpid()) catch '^Vim\%((\a\+)\)\=:E\%(941\|240\)' endtry endif
- or, at least on Unix, calling vim by, say `$HOME/bin/vim` with `$HOME/bin` in `$PATH` and launching
/usr/bin/vim --servername vim -u ~/.vim/vimrc "$@"
If I compile static vim 9.1 (2024 jan 02) I get size of 3.7M
When I compile a static nvi, I get a size of 575K. And the resulting binary segfaults
On NetBSD I use nvi but for Linux I am using vim 4.6
I replaced vim for the vi binary with nvi in my Linux From Scratch fork, thought vim is still left. Yes, my vim is similar in size to yours, good idea for an upgr... - down shift!
http://techinvest.li/tfs/tfs-11.7.html#ch-system-nvi
http://techinvest.li/tfs/ftp/nvi-1.81.6-17-debian.tar.xz SHA256 sum: c146c70e8e954e62d9c26d5319ceb813c2ea316e21d8363ad159c3dbf889f2ec
No doubt it's possible to produce a working static nvi binary for Linux.
The point I was making is that vim requires zero patching. It just works. Even a version from 1997.
[edit: grammar]
I used vim happily for 15 years. When deciding to move on to something else, VSCode won over emacs.
Emacs is fundamentally different, vscode is only convenient if there is no intention to change things.
That said, I use both, and jetbrains.
I think it's important to say that I don't dislike VSC as such at this point. Because I probably made it sound like I think it's terrible. I don't I think it's ok. I didn't mind using it for Typescript as an example. Over all I think it's average at best. I get why people use it, it's easy to setup. It's easy to share configurations and so on. I probably would have gone from vim to neovim if it wasn't for doom emacs though.
I think the major advantage both emacs and vim have though is that they're always good. A lot of VSC users are now switching to Zed and that hamsterwheel will go on and on. With vim or emacs you'll never really have to change anything.
https://github.com/VSCodium/vscodium/blob/master/docs/index....
> Even though we do not pass the telemetry build flags (and go out of our way to cripple the baked-in telemetry), Microsoft will still track usage by default.
I had been jumping back and forth between Vim and Emacs for several years in my hobbyist persona for years. When in hobbyist mode, I prefer to avoid anything that reminds me of my professional mode.
VS and Code are noisy and intrusive. Emacs and Vim (and Neovim) are not.
But I'm pouring water on it right away. I'm glad you found peace with Emacs.
Keep the holy war dead and let people decide for themselves what their editor should be. I use Emacs but I have many colleagues who use Neovim and we all are very supportive of each other.
My choice of Emacs was based on what I see as a fragmenting of (Neo)Vi(m) ecosystem. When writing extensions, I was uncomfortable with a "which of the three languages do I use" decision. The only common language is old Vimscript, and both forks are moving on from it and neither seems willing to support the other fork's preferred language.
That's their right, to be sure. It's just a deal breaker for me.
The resulting increase in height, strength, intelligence, and sexual appeal is no doubt a nice bonus.