Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.
-
Like Aether all over again
Remind me please. I just made an analogy, I want to see if it's the same narcissistic dissonance.
-
The original code was GPL which he illegally re-licensed to creative commons.
fair enough, but that doesn't mean he has to do everything anyone asks him. he's still within his rights to close the source down and obliterate it from the internet. others will come and pick up the torch.
-
The original code was GPL which he illegally re-licensed to creative commons.
If you are the copyright owner you can relicense any way you want learn some copyright law.
-
I don't think you have any projects anyone would use. If you did you could ust tell the imaginary entitled punk you don't have time.
You don't have time to tell them all you don't have time.
-
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. -
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.
wrote last edited by [email protected]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
-
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~
:::wrote last edited by [email protected]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.
