open source software developers are getting fed up and are finally recognizing that they can just fucking leave.
-
@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@micro.webgarden.click @chirpbirb@meow.social this sounds to me like an issue to take up with the package maintainer anyway
I can perfectly understand adding this to prevent a deluge of “help I use old version of $thing why it no work” -
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 When will People stop treating like maintainers of a hobby project owe them anything. I mean yeah, blocking older versions just because isn't that nice, but maybe there is some buggy behaviour you don't see right now.
But nevertheless, it's a project of another person that they kindly shared with you not some Product you paid for. -
@mitsunee @gsuberland @chirpbirb @lianna
or pin an older version, like the maintainer suggested.... -
@alice @lunareclipse @chirpbirb huh, funny coincidence in timeline https://s3kshun8.games/blog/flatpak-won/
@raven667 @alice @lunareclipse @chirpbirb I rather like this writeup because as a Semi new Linux user (4 years and change) AppImage fucking sucks ass, I spent hours and hours trying to figure out how to integrate it into my DE and couldn't for the life of me work it out, because one piece of Software only shipped as an AppImage
-
@alice @lunareclipse @chirpbirb huh, funny coincidence in timeline https://s3kshun8.games/blog/flatpak-won/
@raven667 @alice @lunareclipse @chirpbirb that article read weird to me. Are they saying that all corporations sinking billions into Linux are benevolent? As if the corruption of Mozilla by Google’s money never happened?
-
@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@micro.webgarden.click @chirpbirb@meow.social Considering this isn't a stable plugin, nobody should be using it for anything related to livelihood yet. If someone chooses to do so, that is entirely on them.
-
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 There is more to this story than just those four bullet-points.
-
@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.
@lianna @gsuberland @chirpbirb
Well, it was pretty solid migration path for breaking changes - especially for an _experimental_ plugin:
1.) announce impending breaking incompatibilities - but keep legacy quirks enabled even if that's hindering development
(wait)
2.) give alerts/warning about the really coming breaks when old API is called - still works
(wait)
3.) throw proper errors for legacy API calls instead of silent/unpredictable fails
-
@lianna @gsuberland @chirpbirb
Well, it was pretty solid migration path for breaking changes - especially for an _experimental_ plugin:
1.) announce impending breaking incompatibilities - but keep legacy quirks enabled even if that's hindering development
(wait)
2.) give alerts/warning about the really coming breaks when old API is called - still works
(wait)
3.) throw proper errors for legacy API calls instead of silent/unpredictable fails
@lianna @gsuberland @chirpbirb
Yes: don't ever break APIs.
But while initial development or long life with everchanging input data dependencies (I am looking at you, CKP!), the architecture can be in need of a complete architecture overhaul when the old one proves to be too much of a misfit.
-
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 "I have defended your position on master-main switch."
Wow. That's telling; just not what the commenter thought.
-
@chirpbirb damn maybe people will finally start not taking shit for granted
@lunareclipse @chirpbirb Yeah, right.
-
SOMEONE THINK OF THE CHILDREN!!!
@m @lianna @chirpbirb "Mommas, don't let your babies grow up to be F/OSS maintainers..."
(With apologies to Waylon Jennings and Willie Nelson.)
-
@chirpbirb damn maybe people will finally start not taking shit for granted
@lunareclipse @chirpbirb 0% chance
-
@alice @lunareclipse @chirpbirb @luana I've heard that the duckstation dev is apparently... a specimen.
-
R relay@relay.mycrowd.ca shared this topic
