fs
| vim-treesitter | fs | |
|---|---|---|
| 2 | 1 | |
| 72 | 452 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 2 years ago | 4 months ago | |
| Go | Clojure | |
| - | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-treesitter
-
Vim Boss – Neovim
You are stating these things as though they were established facts. But they seem to be opinions. Or do you have data to back them up?
> People who are new to vim-style-editors and go to neovim are mainly people who would have gone to vim if neovim didn't exist.
It seems reasonable to assume that a lot of new people would not pick up either Vim or Neovim without LSP integration and Tree-sitter.
Vim has adopted a lot of the early features of Neovim and now Vim9 also has virtual text for rendering LSP diagnostics in the buffer[1] and there is a Vim9 LSP plugin too. But it does not at all seem likely that Vim would have these things were it not for the push from Neovim.
Besides, it looks like Vim still does not have mature support for Tree-sitter.[2]
> Well, the prevalent wisdom of 30+ years of FOSS has been that they're mostly bad.
There are many famous forks from the past 30 years that hardly anybody calls bad. Some examples: Net/Free/OpenBSD, GNU/XEmacs, Open/LibreSSL. These projects allowed people with different goals or values to carry on in their own directions, while also motivating each other to pick up development pace. They have often also shared code with each other.
[1] Which looks like this: https://sr.ht/%7Ewhynothugo/lsp_lines.nvim/
[2] One experimental plugin I came across: https://github.com/mattn/vim-treesitter
-
Bram: "Neovim has included Treesitter, which is an implementation of this. Once Vim9 is done I'll have a look at whether it is a good choice to include with Vim"
mattn might be cooking something: https://github.com/mattn/vim-treesitter
fs
-
Vim Boss – Neovim
I'm shocked. I've been a vim user my whole life. I use neovim lately, but I didn't eve know Bram was dead. I've never interacted with him personally, but I've interacted with the tool he wrote and the documentation he wrote almost on a daily basis. Vim is part of me.
I know the project will likely continue, but I can't help but thinking: what now?
It brings up this issue of death in software for me. Software is getting old enough now that it is starting to outlive its authors. RIP Anthony Grimes and Ian Murdock. I have used both of these men's software after their demise[1][2], and I am grateful for it.
However, it does make me think. Grimes' software continues to have issues filed against it[3] by folks unaware that no one is getting notifications for them. On the other hand, Debian was popular enough to continue after Ian's passing, and continues to gain momentum.
I know it might be too soon for me to wonder about these questions to an audience. These were the giants on whose shoulders we continue to work today. I'm glad their code persists.
1: https://github.com/Raynes/fs
2: https://en.wikipedia.org/wiki/Ian_Murdock
3: https://github.com/Raynes/fs/pulls
What are some alternatives?
nvim-treehopper - Region selection with hints on the AST nodes of a document powered by treesitter
NCC - RGBCube's NixOS Configuration Collection.
iswap.nvim - Interactively select and swap function arguments, list elements, and much more. Powered by tree-sitter.
hop.nvim - Neovim motions on speed!
nvim-gps - Simple statusline component that shows what scope you are working inside
Vim - The official Vim repository
vim-treesitter - vim async coloring experiment
nvim-treesitter-context - Show code context