Duckstation(one of the most popular PS1 Emulators) dev plans on eventually dropping Linux support due to Linux users, especially Arch Linux users.
-
Are you smoking crack right now? You sound like you are hopped up on something.
Lol ok. XD sure, why not. You crazy kids.
-
I'm sure that's it.
I'll continue to not use software from mewling babies who blame others because they can't control their own boundaries.
What a whiny baby XD
-
He's a total baby. He gives off big 2000s Windows only user energy
Oh yeah, this guy works for free and doesn't like getting reports for things that are beyond his control, this guy is a huge baby, fuck him for working for free!
You're not paying his salary, he doesn't owe you shit. No liability and all that.
People like you are why open source developers quit. They don't get paid for this, and when it's no longer pleasant, they stop doing work.
-
What a whiny baby XD
Lmao yeah, big projection energy coming from that user.
-
Year of the Linux desktop pushed out a year due to Linux infighting and intolerable advocates for the 33rd year. Clearly the fault of the other distros as I use Arch.
-
Lmao yeah, big projection energy coming from that user.
Just you guys who can't help but white knight this guy XD
-
What a whiny baby XD
Not really applicable, but you do you, Holmes XD
-
Oh yeah, this guy works for free and doesn't like getting reports for things that are beyond his control, this guy is a huge baby, fuck him for working for free!
You're not paying his salary, he doesn't owe you shit. No liability and all that.
People like you are why open source developers quit. They don't get paid for this, and when it's no longer pleasant, they stop doing work.
LoL Jesus Christ, you kids are not alright. XD complete lack of understanding of personal responsibility.
-
Well yes and no you can release them going forward under a new licence. If you obtained your copy under the old license you can use it under the old license when you obtain a new copy you have a new license agreement. Thats absolutly possible to do.
Revoking licenses is alot harder though and changing the lizens from a foss on to another is often confusing and business inapropiate. However it is legal.Assuming newer versions are derived from code that was licensed GPL in the old version, the newer versions (which include new code) are also licensed GPL, whether the person writing the new code likes it or not.
-
I use the Duckstation flatpak funny enough
No, you are harassing and bullying poor Stenzek.
Typical Linux user, using Linux and stuff.
/s
-
Why should he get a say on how someone else installs the software on their own systems?
If I want to build an arch package instead, what business is that of his?
It's open source, the package the developer chooses to distribute doesn't affect your ability to create whatever kind of package for your own system you want.
-
LoL Jesus Christ, you kids are not alright. XD complete lack of understanding of personal responsibility.
complete lack of understanding of personal responsibility
-
Its moments like this I'm glad to be a nixos user lol.
Slap that shit in a flake and forget about it. No matter what updates the dev has, or what system the user has, its always gonna compile.
Fuck I love nix.
If it had genitals I'd fucking date it.
Least obsessed nixos user
-
complete lack of understanding of personal responsibility
Well done using the quote function. Welcome to the internet.
-
It's open source, the package the developer chooses to distribute doesn't affect your ability to create whatever kind of package for your own system you want.
Except this developer has created license terms that forbids the creation of "packages", so he clearly does want to affect my ability to do just that.
-
LoL Jesus Christ, you kids are not alright. XD complete lack of understanding of personal responsibility.
wrote last edited by [email protected]There's zero responsibility or liability on open source work. Specifically, this is licensed as CC BY-NC-ND 4.0, which has the following clauses:
Section 5 – Disclaimer of Warranties and Limitation of Liability.
a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You
b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
https://creativecommons.org/licenses/by-nc-nd/4.0/deed.en
Bref, the developer doesn't owe anyone anything beyond what is stated in the CC BY-NC-ND 4.0 license, the GitHub TOS and the local laws where the developer lives.
-
I'll still be using it regardless..its not like its going to dissappear
-
There's zero responsibility or liability on open source work. Specifically, this is licensed as CC BY-NC-ND 4.0, which has the following clauses:
Section 5 – Disclaimer of Warranties and Limitation of Liability.
a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You
b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
https://creativecommons.org/licenses/by-nc-nd/4.0/deed.en
Bref, the developer doesn't owe anyone anything beyond what is stated in the CC BY-NC-ND 4.0 license, the GitHub TOS and the local laws where the developer lives.
You don't seem to understand what I'm saying, but that's ok.
-
You don't seem to understand what I'm saying, but that's ok.
No, I understand exactly what you're saying, you're stating that people doing free work owe you things, and I'm stating that the licence absolves them of all obligations you claim they have.
Besides, you have not stated on what basis the developer "owes" you support besides attacking them and other commenters in this thread on an ad hominem basis.
If you wanted guaranteed support, you could ask the original author if you can get a maintenance and support contract for their application, where the limits and costs of that support are outlined in the contract.
-
I think he should just drop linux support.
no need to whine or complain.
"not doing linux builds anymore, here is the source, build it yourself if you want", done.
