Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.
-
It doesn't matter what the license say, because GitHub TOS (that everybody agree on when registering their account) explicitly allows forking any project hosted on GitHub, regardless of the project's license.
Copyright is always about distribution. So yes, you are allowed to fork, but you are not allowed to distribute the copyrighted content to other people. And with the No Derivatives clause you are also not allowed to change it.
You might be able to stay in the gray are by telling everyone "build it yourself", but nobody would be allowed to package it either. -
As a linux user myself (arch) I wish the community would just pick a package manager and stick with it.
Seems contrary to the nature of the Linux scene tbh
-
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 mean, he's not wrong, plenty of pre-release games allow you to download before it's out, then android users go and give it 1 star because the servers aren't open yet.
-
The licence doesn't permit derivative works, so no forks and no downstream packages.
wrote last edited by [email protected]It's easy enough to fork the code as it existed under GPL3. Violentmonkey did that when they forked from Tampermonkey.
This dev also doesn't sound like he wants to put much effort into enforcing his license in the first place.
-
It's one of them, and it's fine, but it's not what I've been using. I've been bouncing between PCSX and Beetle and they're both just fine. I mean, at this point PSX games run on anything.
Fair enough. PS2 is still a pain.
-
As a linux user myself (arch) I wish the community would just pick a package manager and stick with it.
Sounds idealistic and raises some questions.
Why? Who decides? Who stops someone from introducing a new package manager? Why should a person developing a package manager be "stopped"?
I don't agree.
Devs could just provide a Dockerfile containing the build environment and a script. That would pair nicely with CI and automated builds.
No need to restrict package managers.
Also, flatpak exists. -
Please. Stenzek is smart but unhinged.
Fortunately, it looks like that was done already with Swanstation, which also has many more contributors.
-
Fortunately, it looks like that was done already with Swanstation, which also has many more contributors.
I hate TwinAphex's guts so I won't use Retroarch/Libretro.
I got mednafen standalone for PS1.
-
Valid points but the maintainer comes off as deranged.
wrote last edited by [email protected]No, Maintainer comes off as pissed off for dealing with a lot of headaches created by others creating a version he doesnt support, and doesnt want, yet is dealing with all the backlash and headache of.
and to try to stem the tide, he created a package just for those people.. and they refuse to use it, continuing to use the broken version, and bombarding him with headaches over something that he, again, does not control.
Only liars would say they wouldnt be pissed off dealing with such a situation.
-
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
Sounds like hes just tired of dealing with idiots.
Which I can sympathise with.
-
He changed the license so no one can legally help him. He kind of put himself in this position. And very likely did so illegally
OK I didn't know that, stupid move on his part then...
What do you mean by likely illegally? -
I hate TwinAphex's guts so I won't use Retroarch/Libretro.
I got mednafen standalone for PS1.
Is TwinAphex still involved in Libretro? Can't seem to find evidence of them from the last few years.
-
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).
wrote last edited by [email protected]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”.
FYI - if you haven't figured this out already (and useful info for other Win32 devs), simply block WM_SYSCOMMAND in your WndProc of your app if the pressed key is SC_KEYMENU.
I've done this for a game mod I'm developing (it didn't have windowed mode originally) and I specifically blocked it only during active gameplay. Otherwise (e.g. during menus) it can be pretty useful to keep active.
-
As someone who used to use arch for years, I can't stand its users who go around acting like running it is some herculean task that takes serious knowledge.
In reality its not much more than a misbehaved pet that requires constant attention and a blog post to be read every month or so. Not because its hard, but because its updates are just kinda slapped together and tossed out in the name of speed.
One of the biggest indicators of this is the AUR. For what it was worth, the Gentoo crowd it replaced at least knew how to compile a program.
Maybe learn to use git, tar, and make like literally anyone else on any other fucking distro.
-
Yeah, PS2 is standalone business still. And in its defense, PCSX2 is super user friendly as a standalone package and supports most of the shared stuff you'd want from Retroarch anyway.
-
No, Maintainer comes off as pissed off for dealing with a lot of headaches created by others creating a version he doesnt support, and doesnt want, yet is dealing with all the backlash and headache of.
and to try to stem the tide, he created a package just for those people.. and they refuse to use it, continuing to use the broken version, and bombarding him with headaches over something that he, again, does not control.
Only liars would say they wouldnt be pissed off dealing with such a situation.
While I understand and respect his feeling, in my limited experience, people that don't like when distributions package their software are often deranged.
Still, if you are using OS packages, your first stop should be OS fora / bug trackers, not upstream. Whoever is producing the distro/OS packages should engage with upstream if and when that's necessary. Upstream, especially small upstreams, really shouldn't be expected to deal with the craziness of Nix, Arch, Debian, and SteamOS all at the same time.
Users are, IME, mostly annoying. Sometimes (not often) I'm glad none of my software has any. At least at work I can point at the Teams / Slack / Jira conversation to prove they specifically asked for something completely different last week and I implemented that.
-
You know, you don't need to censor yourself on here. I don't think anybody's going to be offended if you just write "shit" or "asshole".
I thought they said ahunter2.
-
~11 months ago they relicensed from GPL 3 to CC BY-NC-ND.
Oh. Time for a fork. -ND variants are not Free Software / Open Source.
-
Too many FOSS users are toxicly entitled... It ruins things for everyone.
It's more than just FOSS users. It's "The Internet" in general. At least two of the modding scenes I've been in have had multiple developers (and artists and translators) just quit due to their users aggressively complaining about the stuff they give away for free.
Of course, it doesn't get that much better when people have to pay for things -- ask customer service representatives how much toxicity they see from unsatisfied customers.
-
No, but carrying the grudge this long and vocally leaves me to wonder if the story is as crisp as put forth.
And FOSS die hards put many people off of lemmy early on.
Seek? Yes. Expect? No.
You are the only one here carrying on a grudge and being vocal about it.
Are you a big fan of FOSS? How much are you going to support FOSS developers today hmmm?
