It has been a few days, but I just want to spread the good news that Nvim treesitter is back.
Someone already created a post in the Github discussions. Maybe you guys can show some love there as well.
5ymm3trY 6 points 2 months ago
The project was archived back in April. I assume there were multiple incidents along the way, but the final straw was the discussion in this thread:
Basically it is just people demanding things from open-source developers and behaving like shit while doing so. These guys don't have any respect for the work other people do for free in their spare time.
I use a lot of open-source software, but I usually don't interact with the developers. Whenever something like this happens I feel like we as a community should show our love and appreciation for these projects a lot more, so that devs don't burnout due to this loud minority full of negativity and sometimes just plain harassment.
Dojan 2 points 2 months ago
Aah, cheers for the clarification. I skimmed the github link in the original post, but it mostly seemed like people were happy, and I'd not heard anything about treesitter so it kind of came out of left-field. :)
People acting entitled to the time of volunteers is bananas.
5ymm3trY 1 point 2 months ago
I am no expert either, but my main purpose for treesitter is better syntax highlighting although it does other things as well. I think it is pretty common to use LSP and treesitter together e.g. Kickstart.nvim does it.
Not sure how this relates to autocomplete. For that you usually have things like blink.cmp, coc.nvim or nvim-cmp. I think they mostly work together with an LSP, but maybe they can use the syntax tree from treesitter for that as well.
go to feed...
go to feed...
What happened to it?
save