Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.
-
Valid points but the maintainer comes off as deranged.
-
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.
-
So what other ps1/2 emulators are on Linux yall would recommend. I don't wanna support this dev
For ps2 there is pcsx2 and for ps1 you could try retroarch.
-
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
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.
-
it's honestly why I don't open source any of my projects.
like, I want to make the world a better place but at the same time it cannot cost me my QOL because some entitled punk thinks they can demand shit from me.
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.
-
I just cannot wrap my head around an emulator dev who isn't daily driving Linux...
Damn people are really misunderstanding this comment. Legitimately just don't know anyone who is involved in FOSS projects who doesn't primarily use Linux. Not really passing judgement here, just making an observation.
I'm passing judgement. He's a weirdo
-
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.
The original code was GPL which he illegally re-licensed to creative commons.
-
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~
::: -
Just open source it and leave it to the Linux community.
I understand not wanting to support something you don't use yourself.
He chooses to do direct support over discord vs making people make github issues and wants to whine that this is taxing
-
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.
It would be saner to drop direct tech support than to drop support for an operating system
-
This should be top comment if true.
wrote last edited by [email protected]It is the simple truth
-
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!
Most people arguing from analogies are doing so because they can't actually make a coherent argument against THING so they make a bad analogy and then expect you to unwind the 17 ways the analogy and the thing are different. This being a waste of time. I'll just tell you that your analogy is trash and you should do better.
-
Would have to go back to before the license change in September 2024. The current license basically forbids forks, from my reading.
You cannot forbid forking a public GitHub repository, per their terms of service
-
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.
You can just not publish your actual contacts and choose what you will and wont offer support on your public facing persona.
-
So what other ps1/2 emulators are on Linux yall would recommend. I don't wanna support this dev
Were you supporting him before?
-
I waited a long while to try it
look inside
crash to login manager.
Not sure if you're using some non-proprietary driver or what, but I'm not worried about switching over. Maybe nice with AMD GPU, unlikely for me though.
I don't want GNOME or Plasma (I've had issues with Plasma on X11 when I tried it) so that could be it, too.
I’m on bazzite KDE and haven’t reconfigured anything because everything just ran smooth, but I realise I might be the minority here.
-
wrote last edited by [email protected]
Seems like a skill issue on the part of the dev. GitHub lets you create issue templates and even forms. He could have made it so that every issue creator is warned that packaging issues will be ignored and closed without comment.
"We tried nothing so far and are going for the nuclear option first"
-
As an open source developer, I’d love to have had contributors to help package my apps. It was killing me maintaining everything by myself. It sounds like the control issues I had when I first had contributors, where I didn’t want others to touch my babies too much when people actually started writing code.
Honestly as a dev, I just don't give a fuck. Is that a licence? MIT is close enough.
I let people pr and if it breaks something, oh well. It's not attached to my real name anyway. A good ci/cd saves time and mental energy so I don't have to publish and test. If I bother.
There's some things like onionos that I've helped out with thst I actually take pride in. But it's all for fun. Why not, it's my time. Code will come and go, but I left things a tiny bit better for all y'all.
-
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
"I don't want to get bad reviews so I'm going to be a massive dick to my users"
-
Seems like a skill issue on the part of the dev. GitHub lets you create issue templates and even forms. He could have made it so that every issue creator is warned that packaging issues will be ignored and closed without comment.
"We tried nothing so far and are going for the nuclear option first"
People still don't care. They'll still open packaging related issues. And someone will still have to sift through those and close them individually.
