open source software developers are getting fed up and are finally recognizing that they can just fucking leave.

  • the owner of nvim-treesitter gets a really shitty comment from a user saying that the update to a required version broke their workflow
  • the owner replies saying "hey just pin what you need instead of mainlining it if you need this for an older version"
  • the shitty user replies back saying "go switch to something that doesn't require interacting with people"
  • the owner says "OK." and ARCHIVES THE REPO

https://github.com/nvim-treesitter/nvim-treesitter/discussions/8627

like, holy shit, what a power move.

@chirpbirb To be fair, making an at least somewhat functional plugin crash on some versions just because you don't officially support them is quite hostile and practically malware.

Of course they can maintain whatever versions they want, and the other guy is a dick, but deliberately making it crash when users use it "wrong" is quite toxic. Especially for something as essential as a text editor. Livelihoods could be at stake 

@lianna @chirpbirb

> practically malware

can we please stop saying this. it's patently not true and just waters down the term "malware" to the point where it's useless. there are other terms you can use.

@gsuberland @lianna @chirpbirb
gotta love it when the comments just prove the maintainer right...
@Yuvalne @gsuberland @chirpbirb I guess making people's setups crash if you don't like their software is now completely acceptable in Mastodon reply-guy land. what a wonderful eternal september we're having on fedi
@lianna @gsuberland @chirpbirb
step 1: make an experimental plugin an indispensable part of your workflow.
step 2: ignoring the implications of step 1, use said plugin in an undocumented way.
step 3: bully the maintainer into supporting your unsupported usage.
step 4: ???
step 5: profi– oh nvm we made the maintainer quit FOSS and now the indispensable plugin is abandonware. dang. didn't see that coming.
@lianna @Yuvalne @gsuberland @chirpbirb simply remove the plugin and it stops crashing? a plugin written for a future version of a software is not "malware" when it's being used wrong ​
@mitsunee @gsuberland @chirpbirb @lianna
or pin an older version, like the maintainer suggested....