open source software developers are getting fed up and are finally recognizing that they can just fucking leave.
-
@lunareclipse @chirpbirb @alice duckstation is a completely different story
-
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
Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627
Why there are no releases?
GitHub (github.com)
like, holy shit, what a power move.
@chirpbirb one of my very first interactions online was me bitching about how some version of a Linux audio driver wasn't working with my PC on a forum. I got a response that it was open source and to either pay someone, fix it myself, or shut up. I was 13 and that was 20 years ago. Some people aren't built for this open source life.
-
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
Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627
Why there are no releases?
GitHub (github.com)
like, holy shit, what a power move.
@chirpbirb@meow.social did that back then with a discord modding framework too.
too many entitled kids. -
@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 If ”livelihoods are at stake” then they can do the most basic amount of work required, read the readme and just pin the commit they want. Come on.
-
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
Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627
Why there are no releases?
GitHub (github.com)
like, holy shit, what a power move.
this is insane
i wish good luck and big patience for the dev in their future projects, honestly
-
@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 bailing out with an error message is hardly "making it crash" - and at the end of the day how hard is it to click the fork button and revert that change? Bearing in mind this software pretty much guaranteed to be used by people with development experience.
-
@lunareclipse@snug.moe @chirpbirb@meow.social same as what happened with duckstation
the developer got so fed up with linux users he changed license to one that prohibits distribution (i.e. you can use the provided builds or build it yourself, but not package it) - and ofc linux users respected it and quietly left...
...haha no, they declared the developer the devil, and were (and still are) like: I don't care, you can't stop me@alice @lunareclipse @chirpbirb huh, funny coincidence in timeline https://s3kshun8.games/blog/flatpak-won/
-
@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
> 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.
-
@alice @lunareclipse @chirpbirb huh, funny coincidence in timeline https://s3kshun8.games/blog/flatpak-won/
@raven667@hachyderm.io that's a pretty good writeup
i feel bad for the person who wrote it because of the kind of replies they will get -
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
Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627
Why there are no releases?
GitHub (github.com)
like, holy shit, what a power move.
@chirpbirb based
-
@raven667@hachyderm.io that's a pretty good writeup
i feel bad for the person who wrote it because of the kind of replies they will get@raven667@hachyderm.io what i hate the most about this situaton is - a lot of the people the article is talking about are perfectly reasonable people... as long as linux is not mentioned
like - as a developer who is similarly focused on making a usable app development platform, I'm more familiar with that kind of people than I'd like to -
> 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... -
> 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 ‘literally Hitler’
-
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
Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627
Why there are no releases?
GitHub (github.com)
like, holy shit, what a power move.
@chirpbirb wow, that's almost acting like an adult.
Of course, you have this power and of course you can drop the ball like this, but it doesn't help anyone.
That "power move" is a move you get to make once, maybe twice in your life. Rage quitting a project because one guy asks for it, isn't really building confidence in you.
-
@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 as an eight year maintainer of a packaging tool for a popular programming language there is no fully acceptable way to deprecate features. Someone will loudly, annoyingly complain no matter what path is chosen. From my multiple personal experiences attempting this I will never fault a maintainer’s choice
-
@chirpbirb damn maybe people will finally start not taking shit for granted
@lunareclipse @chirpbirb yeah, as stated in the fucking license, maintainers don’t owe anything to anyone
Some months ago someone was trying to force me to accept their PR, I told multiple times that I will review it anytime soon when I have some energy again
They was still pushy, poking me every couple of weeks, sucking my energy like a vampire
So I took my distance to not suffer and now we’re 9 months later and I don’t give a fuck and will return when I’ll be ready
️ -
@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
-
@lunareclipse @chirpbirb yeah, as stated in the fucking license, maintainers don’t owe anything to anyone
Some months ago someone was trying to force me to accept their PR, I told multiple times that I will review it anytime soon when I have some energy again
They was still pushy, poking me every couple of weeks, sucking my energy like a vampire
So I took my distance to not suffer and now we’re 9 months later and I don’t give a fuck and will return when I’ll be ready
️@lunareclipse @chirpbirb I’m so pissed out of people acting like I am at their complete disposal that my latest works are using this license where the only condition is that there is absolutely no warranty in any way
> Usage of the works is permitted provided that this instrument is retained with the works, so that any entity that uses the works is notified of this instrument.
> DISCLAIMER: THE WORKS ARE WITHOUT WARRANTY. -
@lianna @chirpbirb as an eight year maintainer of a packaging tool for a popular programming language there is no fully acceptable way to deprecate features. Someone will loudly, annoyingly complain no matter what path is chosen. From my multiple personal experiences attempting this I will never fault a maintainer’s choice
@drbrain @chirpbirb I mean, not going ahead actively putting effort into implementing sabotage features to crash setups is pretty easy. The ideal – if not perfect – solution would probably have been a deprecation warning and that's it.
-
@gsuberland @chirpbirb Malware is defined by software with unwanted, unexpected, malicious behaviour. Not every piece of malware needs to result in data breaches or something serious to be malware. Even a jumpscare screensaver is malware per definition.
Intentionally crashing your text editor if the maintainer is upset at your personal setup is pretty squarely in malware territory.
