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

[yuvalne@433.world]

@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.

[m@lgbtqia.space]

@lianna @chirpbirb

SOMEONE THINK OF THE CHILDREN!!!

[tml@mementomori.social]

@chirpbirb I remember back when I did the port of GIMP (and thus GTK and all that it depended on) to Windows, and had a mailing list called gimpwin-users or something like that.

Obviously, there were a lot of entitled users who were angry that I didn't fix their pet bugs very quickly. At around the same time, my own interest in GIMP and GTK was waning, and I had started doing full-time paid work on other open-source things (if I recall correctly). So finally some annoying arsehole pushed me over the limit and I just killed the mailing list. It was such a relief.

[sheogorath@microblog.shivering-isles.com]

@meena @chirpbirb I think you can scratch the rage in my statement and it remains true.

My point is that you should make your departure from a project gracefully, if possible.

Not for this guy who annoyed you, but the others who interacted with you in good faith.

[cyclopentane@rheinneckar.social]

@chirpbirb

>refuses to elaborate
>leaves

[navi@catcatnya.com]

@chirpbirb demanding support without giving the maintainer money is delusional too

[yuvalne@433.world]

@flammableengineering @chirpbirb true, but then we wouldn't be talking about this. if this going viral convinces at least some people to not become ban-worthy dicks, then it was probably for the better for that to happen.

[sam@shonk.sam.ax]

@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”

[niku@fedi.femby.page]

@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.

[yuvalne@433.world]

@mitsunee @gsuberland @chirpbirb @lianna
or pin an older version, like the maintainer suggested....

[prophetscross@mastodon.social]

@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

[eobet@oldbytes.space]

@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?

[thatgalsilver@zoner.work]

@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.

[schmic@hessen.social]

@chirpbirb There is more to this story than just those four bullet-points.

[vampirdaddy@chaos.social]

@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

[vampirdaddy@chaos.social]

@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.

[drwho@masto.hackers.town]

@chirpbirb "I have defended your position on master-main switch."

Wow. That's telling; just not what the commenter thought.

[drwho@masto.hackers.town]

@lunareclipse @chirpbirb Yeah, right.

[drwho@masto.hackers.town]

@m @lianna @chirpbirb "Mommas, don't let your babies grow up to be F/OSS maintainers..."

(With apologies to Waylon Jennings and Willie Nelson.)

[solonovamax@tech.lgbt]

@lunareclipse @chirpbirb 0% chance