41–50 of 80 posts
At this point, vim is hindering progress. While they finally compied almost all of additional features of neovim, there is no sense of innovation and progress there and unfortunately the diff with neovim is right now minimal so neovim loses contributors that would otherwise be
Say what you want about Neovim, but it sure motivated Bram to make Vim better again. Almost everything listed here looks like a direct reaction to features Neovim has added. Same for older releases (async, terminal, etc.). Competition is good and I'm glad we're having it.
At this point, vim is hindering progress. While they finally compied almost all of additional features of neovim, there is no sense of innovation and progress there and unfortunately the diff with neovim is right now minimal so neovim loses contributors that would otherwise be
Sort of like the Gnu Emacs / XEmacs split back then which divided the contributors. At least in case of Emacs one of these came on top, so there is no split anymore.
I switched to NeoVim a few years ago and I'm not entirely sure whether Vim has caught up in features, diverged, or what ratio of the two. That said, I'm not switching back. The only editor I'm really interested in is VSCode. Not that I use it much, but I am very impressed.
May I interest you in https://github.com/neoclide/coc.nvim which let's you use some of the most popular bits of vs code in neovim
I'm using plain vim occasionally, but never tried to do any coding in it, just because I'm not sure how to configure it for that. Which plugins for Python coding are universally agreed on as "must haves" Preferably just one, or two at most.
I'm one of the "computing for the apocalypse" people who try and configure things as little as possible, but I'm really attached to linting in Vim, and I use ALE [1] for this. AIUI it's the standard for asynchronous linting; Syntastic is the synchronous version, but the lag is juuuust a little too much for me.
netrw (Vim's included file browser plugin) has a lot of bugs on macOS, so I use NERDtree there, but have been thinking about looking around at nnn, defx, vim-netranger, etc.
Other than that, Vim has a lot of powerful configuration. It's worth looking around and fixing any immediate pain points you have; odds are there's an option that does what you want. Three cheers for mature software!
Say what you want about Neovim, but it sure motivated Bram to make Vim better again. Almost everything listed here looks like a direct reaction to features Neovim has added. Same for older releases (async, terminal, etc.). Competition is good and I'm glad we're having it.
I switched to NeoVim a few years ago and I'm not entirely sure whether Vim has caught up in features, diverged, or what ratio of the two. That said, I'm not switching back. The only editor I'm really interested in is VSCode. Not that I use it much, but I am very impressed.
Me either.
If you go back to early stories of Bram, the BDFL, when others tried to add Neovim features to vim. He wasn't onboard. Not to discount all the amazing contributions he has done and his importance. But I just think it is karma.
Here is another hacker news post discussing the backstory: https://news.ycombinator.com/item?id=12481084
Here is a bit of shade tossed on the Neovim project back in 2014 by Bram: https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby...
I'm using plain vim occasionally, but never tried to do any coding in it, just because I'm not sure how to configure it for that. Which plugins for Python coding are universally agreed on as "must haves" Preferably just one, or two at most.
Earlier quoted context omitted.
You don't need any for python, really. You can run pdb in your :term split, which is nice. Other than that you only really get the vim advantage over IDE if you practice.
Autocomplete, autoindentation, and perhaps colors would be nice though! To me, the main advantage of vim over IDE is it's there on any remote server.