Skip to content

Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.

Technology
431 192 587
  • Always respect the dev, never respect the user

  • Seems like just repackaging it would solve the problem a lot easier than alienating a userbase- even if small

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

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

    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.

  • 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

  • A dev with some sense.

    Fuck Linux.

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

    One of the most entitled takes I’ve ever read.

    The guy built software and opened sourced it. People started packaging it for their favourite distribution repositories and then users started coming to him for support on problems he didn’t create!

    It’s like if you were a farmer selling eggs and some kids bought your eggs and started throwing them at people’s houses and then instead of the cops arresting the kids they come arrest you for selling eggs. It’s bullshit!

  • A dev with some sense.

    Fuck Linux.

    A dev with some sense.

    I mean, you’re not wrong. The dev does have some sense, not a lot, not a little, just some a very broad some.

    Fuck Linux.

  • I'm all for jerking around on Windows folks to use Linux in jest and fun, but to purposely shit on a major contributor of any foss for not using Linux makes my blood boil.

    honestly, I hope the dev reads this and takes my advice.

    as a Linux guy, run dude. fuck these assholes. they don't deserve your time, your talent, or your efforts. gank your shit, rewrite the license, and block any Linux use. and make sure you call out the distro(s) responsible. sometimes assholes have to be put in their place to learn anything. even then, if history tells us anything they're just going to go poison some other poor dev and forget about you.

    Not really sure how you read my comment as "shitting" on anyone. I'm just commenting that it's unexpected and unusual for a FOSS dev to not be Linux user. Idc what they do, just making the observation as someone involved in the FOSS space that most of my peers are more likely to shit on windows than Linux.

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

    It was if I remember right, just not by the dev

  • Hi, I'm a subsystem maintainer for the Drupal project, a security team member, and over the years have helped maintain several of the largest projects in the ecosystem. I've also contributed to a number of open source projects over the years and have a lot of experience collaborating with maintainers to get fixes committed going back to early amd64 fixes coming out of testing in the gentoo project before Intel even had a real 64bit platform. I've got a pretty good feel for how this works and it's safe to say FLOSS is kinda my day job.

    cool story random internet person. totally believable.

    I'm a debonair surgeon with a heart of gold that loves long walks on the beach when I'm not sipping martini's in my robe while strolling around my compound. I have single handedly operated on soldiers as well as pulled many humorous pranks on my colleagues to make the front line not seem so god awful. between the booz and the boobs around camp it's safe to say I'm a doctor of love and my prescription is fun fun fun!

    ::: spoiler here's a real picture of me.
    1000001824
    :::

  • One of the most entitled takes I’ve ever read.

    The guy built software and opened sourced it. People started packaging it for their favourite distribution repositories and then users started coming to him for support on problems he didn’t create!

    It’s like if you were a farmer selling eggs and some kids bought your eggs and started throwing them at people’s houses and then instead of the cops arresting the kids they come arrest you for selling eggs. It’s bullshit!

    How does that analogy make any sense? No one has done anything malicious to him. He released open source software, got mad and revoked the open source license for newer versions, then got even more mad when people continued using the old open source version. Which is a problem he brought on himself. And his continued tantrums still won't keep distros from packaging the only version they even can package.

  • Seems like just repackaging it would solve the problem a lot easier than alienating a userbase- even if small

    .

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

    TIL dolphin can emulate psx.

  • 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

    Can you help me underatand where you proved him wrong?

  • How does that analogy make any sense? No one has done anything malicious to him. He released open source software, got mad and revoked the open source license for newer versions, then got even more mad when people continued using the old open source version. Which is a problem he brought on himself. And his continued tantrums still won't keep distros from packaging the only version they even can package.

    He got mad because people kept bugging him to fix problems created by other people which he has no control over. His “tantrums” are his way of re-asserting control over his life.

    Open source dev burnout from support requests is a real and widespread phenomenon. When a software developer releases the fruits of their hard work they are doing the wider community a service. When large numbers of people begin to contact the developer for support the effect can be overwhelming even though every individual request may be legitimate and non-malicious.

    In the case of packaging errors created by a third party not in contact with (let alone under the control of) the developer, these support requests for dealing with unsolvable and irrelevant (in the developer’s eyes) problems can be absolutely maddening.

    I am quite sure the developer would have had no issues with people doing what they did as long as they accepted the responsibility to fix their own issues without contacting him. The fact that they did not do so (and therefore caused him grief) is negligent even if it isn’t malicious.

  • Valid points but the maintainer comes off as deranged.

  • cool story random internet person. totally believable.

    I'm a debonair surgeon with a heart of gold that loves long walks on the beach when I'm not sipping martini's in my robe while strolling around my compound. I have single handedly operated on soldiers as well as pulled many humorous pranks on my colleagues to make the front line not seem so god awful. between the booz and the boobs around camp it's safe to say I'm a doctor of love and my prescription is fun fun fun!

    ::: spoiler here's a real picture of me.
    1000001824
    :::

    You got me, I'm impersonating some other neclimdul guy that's easily Googleable and matches the description I gave. I registered this account two years ago and participated in discussions all this time so I could trick you specifically Hawkeye. You really did call me out. Good one.

  • Not really sure how you read my comment as "shitting" on anyone. I'm just commenting that it's unexpected and unusual for a FOSS dev to not be Linux user. Idc what they do, just making the observation as someone involved in the FOSS space that most of my peers are more likely to shit on windows than Linux.

    you didn't make an observation. you made a statement. you stated that it's impossible to fathom why anyone doing foss would continue using Windows over Linux.

    it's not impossible, you just choose to disregard their personal preferences.

  • You got me, I'm impersonating some other neclimdul guy that's easily Googleable and matches the description I gave. I registered this account two years ago and participated in discussions all this time so I could trick you specifically Hawkeye. You really did call me out. Good one.

    you act like it's impossible for anyone to go register that name.

    I don't know who you are. I didn't even google your name because I really don't care enough who you claim to be.

    my point is, your original comment called him out as petty and even so I believe that's warranted. if a group of people are using the tools that he created in a way that he doesn't like or want, is he not entitled to make a change to stop that from happening?

    at that point the whole community could fork the repo and do their own thing. but no, entitled shitlord users want to post ragebait shitposts and call the dude an asshole for putting his foot down and drawing a line because he's had enough of entitled shitlord package managers.

    the guy didn't do anything wrong, because as the maintainer he has the sole responsibility and vision of where he wants to take his project. the community isn't wrong is forking it either.

    the only people who are wrong are the ones calling him a petty bitch asshole for doing the thing he's supposed to do!