- I will never understand people like GitHub user “shushtain” in the linked issue.
So obviously the guy is behaving like an entitled jerk, but it’s also surely counter-productive (volunteer maintainers are unlikely to respond well to plain rudeness)? Unless the goal isn’t a productive outcome, but just to be mean?
by ivanjermakov
1 subcomments
- This is a bane of all such aggregator libraries, that suck maintetance from other projects into themself. Null-ls suffered from this, too: https://github.com/jose-elias-alvarez/null-ls.nvim/issues/16...
The source of a library needs an update every time there is a configuration change in _any_ tree-sitter parser supported.
The only sustainable option is not use these helpers and manage editor dependencies manually: tree-sitter parsers, LSP servers (looking at you Mason), and plugins (looking at you neovim distros).
- Good for the maintainer, hope they find peace and do things just for their fun, without needing to deal with comments like that anymore
- This was probably near the breaking point before, it just needed an idiot to catalyze.
by bedroom_jabroni
0 subcomment
- Incredibly based response to the "I am the customer" energy in OSS.
- Nvim treesitter is kind of taken for granted even if nvim maintainers say it's experimental. So I think the community will have to find a solution and replacement project.
- > since people apparently can't read
I know Free and OpenSource software is only available thanks to maintainers who spend their time and money to make it available.
This type of sentence though, makes all I just mentioned easy to forget, when they take that tone with you.
- I get anxiety publishing open source because of things like this.
- idgi, shitting on the maintainer takes 10x more time than forking the repo
I guess he really needed the latest ci/chore commits
- Genuine question: Why not just close such derailing and burdensome issues and/or block mean people?
My guess: People would freak out if FOSS maintainers actually did this.
- Isn't treesitter integrated to nvim anyways at this point, even if it's experimental support?
- The Fandom Menace strikes again.
But seriously, this is messed up. People need to learn to treat others with respect and kindness. Hopefully the maintainer is able to simply move on after archiving the repo, and isn't dealing with any mental struggles from dealing with years of entitled users demanding things for free.
In popular open source projects this is a recurring issue. I suspect the only way to deal with it is to either shift to a platform that has better tools for moderation, or end the project like the maintainer has done. Let someone else fork it and deal with the users.
To clason: Thank you for all the work you did maintaining nvim-treesitter!
- Will this mean the end to NeoVim, whose main (one of) selling point is the tree-sitter out of the box? I hope not, as I am the long time user and supporter of the project.
- It’s like the law of big numbers. Once a project grows large enough, some entitled free-riders are bound to pop up.
What to do as maintainer? Can everyone of them find piece?
by potatosalad99
0 subcomment
- Honestly this is just a case of open source software users expecting a free lunch. Firstly, the maintainers of this package don’t owe you anything, secondly the new version of neovim and treesitter-cli are already in Arch extra testing, and since they don’t break anything they’ll probably be in extra next week, so chill the fuck out.
If you have a problem with how open source works just please head back to vscode.
by hacker_homie
0 subcomment
- Honestly I missed the neovim 12.0 being marked stable, and just updated when this happened.
- So what will happen now? Who will take over? Abandoning a project because 1 person is kinda extreme.
by porridgeraisin
0 subcomment
- This is why I built nvim from source, and git pull plugins into the pack directory. I think it's even a static binary. Whatever changes I need I git pull. After they added LSP I have not wished for anything else really, so I stopped pulling. I think I pulled LSP completion API in 0.11 era but that's it.
Hate it when people break backwards compatibility. For me it's sacrosanct, more important than absolutely anything else.
I only have a handful of plugins so the system works well. And I have a 500 line init.vim (and no other config).
Some ecosystems like golang share this principle and so I can freely update packages without worrying about breakages. But other ecosystems(nvim, python, etc) I'm a lone warrior
Hacker News