Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.
Technology
370
Beiträge
170
Kommentatoren
554
Aufrufe
-
People just expect open source devs that do this shit in their free time with absolutely no compensation to bend over for them and do everything they please. The good thing about open source development is that you can just help with the development yourself.
I'd go further, you should help with the development. Seems like some people would rather spend hours hounding a developer to implement their thing, rather than figuring out how to do it themselves...
-
Can you help me underatand where you proved him wrong?
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
-
So what other ps1/2 emulators are on Linux yall would recommend. I don't wanna support this dev
If you care about RetroAchievement support, this is what they support.
Beetle is the RetroArch core that's most often recommended. If you don't like RA (they have serious issues of their own), the Beetle core comes from the emulator Mednafen.
And the other main open-source option is PCSXR.
-
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.
"It's impossible" is often used not to literally describe a logically impossible event but instead as an exaggeration. "I can't possibly fathom why" is also not literal, it means under regular circumstances.
I cannot imagine why anyone would prefer grass that cuts your skin over regular grassmeans for typical people using grass in typical garden/field situations. That could be someone's person preference but that it's not typical, it's unexpected. -
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!
really don’t care enough who you claim to be.
You asserted pretty matter of fact who I was starting this discussion but ok.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?
In short no. At least not if you're software is GPL, then you don't have any say in how its used. Its the bargain we make when we choose an open license as it specifically grants the right to use software freely. So up to last year, he has no say in how its used. And honestly, If download and compile the CC version today he doesn't get any say either. For the most part even proprietary software like Windows don't get a lot of say in how things are used either if you pay for it.
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
There are forks of the GPL code. They're in the fork tab in github. Also a trip to google finds this version https://github.com/libretro/swanstation which appears to have been forked for 4 years now. There are also other PS emulators that seem more popular in things like retropie where it would be more widely distributed so not sure how much interest there actually is.
because he’s had enough of entitled shitlord package managers.
Genuine question, what did the package managers do that's so "shitlord"? I can guess about bug reports or complaints about licensing(guess because issues are closed) but really don't know what he's mad about the packaging thing. There are some community aur's but they seem fine.- duckstation-git "most popular" clones the github source and compiles it locally. Its downloading the source directly so can't be any more unmodified and allowed under the restrictive CC license.
- duckstation-qt-bin downloads the app image from the official github and extracts
- duckstation - Also builds from source but pinned to old gpl release. looks to patch and update some libraries for compatibility? GPL code so modifications fair game.
- duckstation-preview-latest-bin also just downloads app image and extracts
So none of the aurs distribute anything built on arch infrastructure, its all unmodified versions exactly like his license and readme specify.
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
Sure, he can do what ever he wants I guess. Accept what ever PR, commit what ever code. He can even delete everything tomorrow(I believe he's done it before?) because he thinks neclimdul specifically is a jerk and was mean to him on lemmy and no other reason. That doesn't make his decision good or reasonable or right. I mean you don't seem to like me but I hope you get my point.
But just to really be clear why I think this was a jerk move, https://github.com/stenzek/duckstation/blob/master/CMakeModules/DuckStationBuildSummary.cmake#L38
This doesn't block packaging, it blocks compiling on any arch system. Its a poison pill because he didn't like some people using a specific distro and doesn't really affect me but strikes me as pretty petty.
-
Valid points but the maintainer comes off as deranged.
If I give something for free, it's my rules. Simple as that. Don't like it? don't accept it.
Linus is often a dick. He even acknowledges it. Don't like it? Well, there are other OS.
I'm not like that, I like being helpful, I actually do many volunteer hours a week, but...
I do hate entitlement. I don't see these people giving Microsoft as hard a time.Lets keep the Karen constrained, please.
-
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
it genuinely seems like this guy hates developing duckstation at all.
I don't think you get it. He probably enjoys creating, and achieving something awesome. He has no obligation to deal with entitled users of what he gives away
-
If I give something for free, it's my rules. Simple as that. Don't like it? don't accept it.
Linus is often a dick. He even acknowledges it. Don't like it? Well, there are other OS.
I'm not like that, I like being helpful, I actually do many volunteer hours a week, but...
I do hate entitlement. I don't see these people giving Microsoft as hard a time.Lets keep the Karen constrained, please.
Yeah but you also don't get to be upset if someone calls you unpleasant. Both things can be true.
-
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).
-
If you are the copyright owner you can relicense any way you want learn some copyright law.
yes you can!
...for new versions. not for already released ones.
at least not with most common copyleft/open source licenses.
edit: assuming a solo project. see below.
-
If you are the copyright owner you can relicense any way you want learn some copyright law.
This is true, but it's also true that the older gpl versions can't be revoked.
-
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.
Is the issue with the packaging, or that only an outdated version can be packaged?
He could fix the license, then people would push the up to date version and users wouldn't report old bugs.
-
Linux pros: FOSS, free, private, secure, etc.
Linux cons: Linux users
-
it genuinely seems like this guy hates developing duckstation at all.
I don't think you get it. He probably enjoys creating, and achieving something awesome. He has no obligation to deal with entitled users of what he gives away
Then he really shouldn't have a discord server where he offers tech support.
It's one thing to not give anyone lemonade, you're never obligated to do that for no reason, however it's another thing to set up a free lemonade stand and tell whoever tries to get lemonade that they're annoying and to go away.
-
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.
::: spoiler can I say something a little stupid
Thx!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~
:::Most arch users are casuals that finally figured out how to read a manual. Then you have the 1% of arch users who are writing the manual…
It’s the Gentoo and BSD users we should fear and respect, walking quietly with a big stick of competence.
-
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).
GNOME devs however should stop forcing their UX ideas onto others
And then break them with every major release
-
The overwhelming majority of Linux users are on 4 distros + derivatives. Debian Fedora Arch Suse not "thousands"
Where would what end? Most actually open source projects just publish releases to source and provide as much or as little support as they feel like. Slap a github issues page up and tell every user that you are only interested in dealing with bugs in the most recent version in whatever official channel you prefer eg provide appimage of releases and insist that users reproduce and document bug.
Time wasted mostly wont even bother to create a github account and if they do close issues if they can't follow directions.
.
-
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.
::: spoiler can I say something a little stupid
Thx!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~
:::I don’t know how many tutorial I saw about compiling arch
2 things wrong with that:
- No end user compiles ArchLinux from source
- One of the first things you're told when using ArchLinux is to peruse the Wiki, not "many tutorial"
You don't know what you're talking about.
-
Most arch users are casuals that finally figured out how to read a manual. Then you have the 1% of arch users who are writing the manual…
It’s the Gentoo and BSD users we should fear and respect, walking quietly with a big stick of competence.
As a 10 year Arch user* I concur. Reports of danger are vastly exaggerated. Most software comes pre-compiled and tested. I never had any more (or less) problems than with Debian stable.
Newcomers often underestimate the importance of its wiki, and some are perpetually unwilling to understand.
-
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
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,”
This sounds like there were several users berating you, not (just) the developer?
It's a tricky one. You can't ban every user from your Discord just for being condescending.
-
From games to reminders to drink water: The rise of 'streaks,' rewards that keep you hooked
Technology
1
-
-
-
Hong Kong workers strike against the algorithmic exploitation of Keeta, a food delivery platform
Technology
1
-
NO KINGS! Tomorrow on Trump's birthday, we protest across the entire nation. Check the website for No Kings events near you!
Technology
2
-
-
Reddit sues Anthropic, alleging its bots accessed Reddit more than 100,000 times since last July
Technology
1
-
