170
submitted 2 weeks ago by Pro@reddthat.com to c/technology@lemmy.world
top 50 comments
sorted by: hot top controversial new old
[-] GreenKnight23@lemmy.world 74 points 2 weeks ago

itt: a bunch of entitled Linux youths that don't understand burnout or QOL.

dude has set a limit to what he wants or is willing to do. still gets called a bitch for defining the line and is still called an asshole.

some of y'all even bring up multiple cases of other foss devs doing/saying the same thing, continue to call them assholes.

🤔 There's a pattern here...but I'm just too blinded by the brilliancy of my distro to see it...

[-] yetAnotherUser@discuss.tchncs.de 32 points 2 weeks ago

Notice how the developer argues he forbids packages and how the AIR is in violation of this? But an AUR PKGBUILD is not a package - it's build instructions. It doesn't distribute or package anything, you can check it yourself. It's not called "PKG" for a reason. He misunderstands his own license and believes the allegedly broken PKGBUILD violates it.

He may be right about some users annoying him with bug reports though I'd be surprised if it was that common. It seems like he got a couple of reports, noticed the "forbidden" PKGBUILD and then reacted like this. Just like when changing the license from GPL to CC-BY-NC-ND in order to combat... GPL violations and trademark infringements?

Frankly, the project has not had parricularly stable leadership in a while. Though a bit unfair of a comparison, compare it to Dolphin and you can see a night and day difference in project management.

load more comments (2 replies)
[-] douglasg14b@lemmy.world 17 points 2 weeks ago

Seriously, this thread is honestly vile and these people are a perfect example as to why this is happening.

How they are this blind to their own toxicity is beyond me

[-] michaelmrose@lemmy.world 23 points 2 weeks ago

I haven't read anything VILE here. It's happening because he's both controlling and implicitly bad at maintaining said control. Had he not insisted on trying to control packages he would have had a working package like every other software project in the ecosystem that is properly maintained for free by other people's labor.

load more comments (5 replies)
[-] DaTingGoBrrr@lemmy.world 9 points 1 week ago

The problem has originated because he changed the lisence resulting in older versions being the only way to ship duckstation.

load more comments (26 replies)
[-] whaleross@lemmy.world 63 points 2 weeks ago

Gamers can be the most entitled demanding assholes. Arch users can be the most annoying arrogant and conceited people to exist online.

I wouldn't dare imagine dealing with the unholy mix of arch gamers min-maxing social skills for inferiority complex.

I'd rather drop support too.

[-] mesamunefire@piefed.social 11 points 2 weeks ago

Is there a specific interaction that made them angry?

[-] woelkchen@lemmy.world 121 points 2 weeks ago

Is there a specific interaction that made them angry?

Stenzek's feeling got hurt when DuckStation was still proper open source software and people used the software fully in accordance with its license, i.e. they distributed modifications and not all permitted modifications were the most polished ones, so he felt that they give his name a bad reputation. Again: Stenzek released DuckStation under a license that explicitly allows this.

So he rage quit open source and released new DuckStation versions under a very restrictive "source available to look but not touch" license that's so insanely restrictive, Linux distributions are not allowed to make their own packages. So they ship the old version that works just fine because PlayStation 1 emulation was figured out very long ago. Stenzek feels that they should not ship the old version (which they are fully entitled to) and instead make a special exception for his software alone to point their users to DuckStation's website where instead of acquiring the emulator from their package manager (or "app store" in case you're not familiar with that term), Linux users should take extra steps to manually download and install DuckStation.

And since users may not know about this rift, they may post bug reports and feature ideas to Stenzek, even though these bugs may have been long fixed by non-open source DuckStation.

Basically: Stenzek did not read the license he picked for his software and then got mad when people made use of provisions explicitly allowed by the license.

[-] unexposedhazard@discuss.tchncs.de 25 points 2 weeks ago* (last edited 2 weeks ago)

This should be top comment if true.

[-] brucethemoose@lemmy.world 25 points 2 weeks ago

This is a great case for a “reader added context” feature for Lemmy, if it could be implemented in a decent way.

load more comments (1 replies)
load more comments (1 replies)
[-] brucethemoose@lemmy.world 20 points 2 weeks ago

This happens way too much.

“What? People are doing things with my Apache project I don’t like!?”

load more comments (11 replies)
load more comments (5 replies)
[-] FunnyUsername@lemmy.world 31 points 2 weeks ago* (last edited 2 weeks ago)

this developer is a big prick. i had an issue (that turned out to be user error after getting help from another source) with the android version of duckstation so went to their discord for support. instead of offering any aid or insight, i was immediately stereotyped as "an android user" and told "we don't offer tech support for android" basically for no other reason than "because android users bitch too much and then give you a bad review," which is just kind of insane imo? there's no downside to bad reviews like you're not going to get delisted? anyways, completely not surprised to hear this from that ass. it genuinely seems like this guy hates developing duckstation at all and i am confused why he bothers. give it up man, sounds like you'll be happier

[-] APassenger@lemmy.world 13 points 2 weeks ago

Can you help me underatand where you proved him wrong?

[-] scratchee@feddit.uk 8 points 1 week ago

Who said he was wrong? He basically guaranteed that android users will respond that way by refusing to support them, thus ensuring he will always be right about them

load more comments (6 replies)
[-] Feathercrown@lemmy.world 11 points 1 week ago

"I don't want to get bad reviews so I'm going to be a massive dick to my users"

load more comments (13 replies)
[-] eldebryn@lemmy.world 31 points 2 weeks ago

While users can be demanding, this reads like a very immature response. Going out of your way to block support and prohibit packaging, which you can let others do with 0 seconds of your time, is kinda rude.

Author may have been harassed for all I know, but this is still an emotional response. They could have just said "yeah I'm not supporting this at all, figure it out yourselves if you want to" rather than actively blocking Linux functionality/packaging, which is what this sounds like.

load more comments (6 replies)
[-] ZILtoid1991@lemmy.world 29 points 1 week ago

Dev here who also happens to support Linux, and while Linux has its own challenges (whoever came up with the libevdev API, should not allowed to come up with any other API's), I think it's good to support Linux natively regardless. GNOME devs however should stop forcing their UX ideas onto others sometimes even outside of Linux. One of them when I was asking about how to I make the Alt key on Windows to stop it trying to open the nonexistent menu bar, then they told me to "just add one". I'm developing games, not just desktop apps, where the alt key isn't expected to open a menu bar. I then got told that it's "expected behavior" (Hungarian here, I'd like to expect that both alt keys are for accessing a second set of gliphs, and one of them isn't a dedicated "menu key"), and that games like Unreal Tournament "did it already" (that one used the escape key for menus).

[-] A_norny_mousse@feddit.org 20 points 1 week ago

GNOME devs however should stop forcing their UX ideas onto others

And then break them with every major release

load more comments (6 replies)
[-] ArchmageAzor@lemmy.world 24 points 1 week ago

Linux pros: FOSS, free, private, secure, etc.

Linux cons: Linux users

load more comments (3 replies)
[-] Mondez@lemdro.id 18 points 2 weeks ago

I think this should have been anticipated after the license change.

[-] nickwitha_k@lemmy.sdf.org 9 points 2 weeks ago

Yeah. That's a pretty shitty license to move to for endusers and others. Disallowing derivatives, etc. is within their rights but, really a dick move but, considering this commit message, not surprising.

[-] deadcade@lemmy.deadca.de 9 points 2 weeks ago

It's actually not within their rights (I am NOT a lawyer)

GPL code is still owned by the person who wrote it, that includes contributors who have made a PR. Unless they all signed CLAs (Contributor License Agreements) to hand over their copyright to the repository owner, the repository owner does not hold copyright for this code, and as such can't legally change the license. They can use and distribute it as specified in the license terms of the GPL, but that excludes changing the license.

load more comments (5 replies)
load more comments (1 replies)
[-] drmoose@lemmy.world 15 points 2 weeks ago

Valid points but the maintainer comes off as deranged.

load more comments (7 replies)
[-] A_norny_mousse@feddit.org 10 points 2 weeks ago
load more comments (1 replies)
[-] Vitaly@feddit.uk 10 points 2 weeks ago
[-] missingno@fedia.io 31 points 2 weeks ago

This is the dev that changed the license a while back from GPL to CC-BY-NC-ND because they got mad about forks.

The kicker here is that the AUR package they're whining about here is based on the last GPL version.

[-] Sanctus@lemmy.world 21 points 2 weeks ago

So he fucked his own packaging with the licenses and now blames the users for complaining? Common Windows Dev L

[-] A_norny_mousse@feddit.org 12 points 2 weeks ago

changed the license .. from GPL to CC-BY-NC-ND

oof. Good luck with that in FOSS world.

[-] bdonvr@thelemmy.club 9 points 2 weeks ago

I can sympathize with being frustrated but that's silly

load more comments (4 replies)
[-] mesamunefire@piefed.social 9 points 2 weeks ago* (last edited 2 weeks ago)

Yeah im sure someone will fork and it will be named chickensation or whatever. Then we will move on.

Hope the developer feels better. Its easy to get burnt out on passion projects. If I were to guess, this is what is happening. They are going to say some pretty insane things in the next couple of weeks and then get a handle on their life.

Ive always liked: epsxe myself. Works well and no real drama. Its a very old console.

[-] woelkchen@lemmy.world 12 points 2 weeks ago

Yeah im sure someone will fork and it will be named chickensation or whatever. Then we will move on.

https://github.com/libretro/swanstation

load more comments (2 replies)
load more comments (12 replies)
[-] neclimdul@lemmy.world 9 points 2 weeks ago

Imagine if Linux developers building the libraries this was built on where as petty.

[-] neclimdul@lemmy.world 7 points 2 weeks ago

Petty is pretty harsh and reading this message I wish I'd paused and chosen a better word.

That said, the way the commit reads, the relicensing, the fact they seem to be upset the aur is locked to the GPL version to comply with the license but also poisoning the build scripts like it's somehow going to affect the old GPL code. It just does not sound like someone acting in good faith with the open source community they're clearly building on top of and that does rub me the wrong way.

load more comments (7 replies)
[-] IzzyJ@lemmy.world 9 points 2 weeks ago

So what other ps1/2 emulators are on Linux yall would recommend. I don't wanna support this dev

[-] Agent641@lemmy.world 14 points 2 weeks ago

Were you supporting him before?

load more comments (2 replies)
[-] danhab99@programming.dev 9 points 2 weeks ago

This is so lame for the arch community, like I use arch btws are supposed to be the most hardcore power users and they bugged a dev that badly! I don't know how many tutorial I saw about compiling arch and building everything yourself into a minimal setup.

You can't give me shit for using Manjaro for as long as I did, GLAD I LEFT.

can I say something a little stupidThx!

So I don’t think there’s anything inherently wrong with ignoring emails. Emails are a kinda public way for anyone to start a conversation with you. As developers, we include our emails in commits — but we don’t have to. I don’t think GitHub even checks whether the email addresses in commits are valid.

So yeah, if you have a valid reason to reach out to a developer, go ahead. But if that developer disagrees or doesn’t want to respond, that’s just how it is — you can’t make someone email you back.

I’m just being consistent with myself. I always tell my friends and family about the importance of the block button, and I’ll say the same thing here: just ignore it. And in this case someone would have eventually fixed the problem and submitted a PR.

~sry if I was condescending~

load more comments (3 replies)
load more comments
view more: next ›
this post was submitted on 30 Jul 2025
170 points (95.7% liked)

Technology

73970 readers
740 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS