[roarcher]

You're confused. I'm not talking about using your GPL code in my project. I'm talking about why I choose not to license my own project as GPL.

Edit: Nice ninja edit. No, I don't use non-copyleft licenses for bragging rights. What is it with GPL ideologues in this thread and ascribing ulterior motives to anyone who disagrees with them? Here's why I don't use copyleft: because I don't give a shit who uses my code or for what. It's really that simple. I guess I don't have enough petty envy in me to care if, god forbid, somebody else makes a buck off my code.

And so what if some corporation blames me for bugs? I can tell them to fix it themselves or pound sand. That's the beauty of requiring nothing from them in return. They have no leg to stand on when making demands of me.

[B8MGHCBekDuRi]

did you or did you not write these sentences?

> Other than an appeal to their sense of morality (which only works if they happen to be a Stallman disciple)

> what's their incentive to use it? It's simply demanding more from those who are already giving.

I think you meant more than simply "why I choose not to license my own project as GPL"

you're actually bashing on GPL because you either

- are ignorant of what GPL license says

- have an agenda and/or are paid to spread FUD

- all of the above

If I want to be charitable I would say that the last hypothesis is that you are not aware of what you write.

EDIT:

you also rote

> Nobody is "afraid" of copyleft, that's a rhetorical device you're using to discredit those who disagree with you

Which is not true, a lot of businesses are afraid of copyleft, in fact at work not many people can publish their code under a copyleft license, because the mainstream mindset is that code is an asset and keeping it secret gives companies an advantage. Which clearly is not the case, because most of the code is simply a rewrite - usually bad - of something that already exists in the copyleft World. Everyone working in the field knows that. So it's a decision based on fear not on risk assessment. The company I work for is specialized in risk assessment and even they cannot escape the myth that code must be kept secret or the competition would steal it. I wonder what competitor would steal that pile of garbage that only works under very specific requirements, which are mostly there because 40 years of legacy and incompetence.

You seem to have an idea of copyleft (GPL in particular) that is far from what it is and it only exists in your mind.

[roarcher]

> I think you meant more than simply "why I choose not to license my own project as GPL"

Think what you want. Nobody else was confused by my meaning.

> have and agenda and are paid to spread FUD

LMAO you guys are fucking lunatics. Have a nice night.

[B8MGHCBekDuRi]

> Think what you want. Nobody else was confused by my meaning.

you are very confused and don't even understand what you wrote my dear friend.

GPL is not based on "asking those who are already giving to give more" but on collaboration. Which I understand is not a thing for you, so you better stay away from it, but that's not a GPL's fault, that's exactly the purpose: keeping away the free riders like you!

besides "nobody else" is a very poor defense, only kids use that. It doesn't make your statements less false.

> LMAO you guys are fucking lunatics. Have a nice night.

Who are you talking to now?

I am one.

Reminder: the World is vast, USA is just a small percentage of it, not even one of the most interesting by any metric, it's lunch time here.

Sleep on it, if tomorrow you still see the invisible "guys" you mentioned, call a doctor. You sure you're ok?

[quectophoton]

To me the only open source license that seems to make sense without imposing on other developers, is the MPL without copyleft exception:

"Do what the fsck you want with your code; as long as my code and any modifications to it are available under the MPL, I don't give a sheet what you do with the rest of your code."

Also, when another license is incompatible with the GPL, I see it more as the GPL being at fault, because it's literally only compatible with itself unless you explicitly add exceptions. It doesn't matter if another license grants the exact same freedoms as the GPL, it will be incompatible with the GPL because it has a different name.

[B8MGHCBekDuRi]

> What is it with GPL ideologues in this thread

so if you chose BSD you are exercising your freedom, if people use the GPL the way it was intended, they are lunatics or ideologues.

Nice try, little "Nazi schatze" who "fight for fatherland" (cit).

> what. It's really that simple. I guess I don't have enough petty envy in me to care if, god forbid, somebody else makes a buck off my code.

except that there are INNUMERABLE cases of people having created very successful projects (please provide proof that your code served more than yourself) that are lamenting the fatigue of maintaining it while commercial entities make a lot of money out of it, without giving back, not even pennnies, let alone workers or code.

That's why GPL has its merits, it prevents this kind of behaviour which is to be expected from corporations and other private for profit entities.

If you think that's ideology and your case will be different, you're simply delusional.

As soon as 20 people will start using your code and file bugs, ask for features, open issues on something that is not related in any way to what you wrote, because they did not understand it or were told to nag you, you'll lose your shit. 100% guaranteed.

For what?

[josephg]

> there are INNUMERABLE cases of people having created very successful projects that are lamenting the fatigue of maintaining it while commercial entities make a lot of money out of it, without giving back, not even pennnies, let alone workers or code.

Hi, people have made money using my code and I also don’t care. I’m happy more people are using my software. I like the bragging rights and I’ve gotten plenty of work off the back of my opensource work. I understand this is upsetting to you. If you don’t want people using the software you write for free, maybe don’t write free software? That’s sort of the point.

There is a problem of freeloading in the opensource world - we need better ways to fund opensource code. But I don’t see how the GPL is a viable solution to that problem. Not at all. More likely, if I release my code under the GPL not only won’t I get paid, but also nobody will use my software. That sounds like a strategy which just makes everyone lose.

[B8MGHCBekDuRi]

> Hi, people have made money using my code and I also don’t care

looks like everyone's missing the point.

> I understand this is upsetting to you

Again, maybe I am on another level of comprehension, so I don't understanda why it is so hard for someone to get it, but I am not upset by that, at all.

I simply know that those who think "it will be fine" are delusional and don't know what they are talking about!

So I just will paste some link to relevant news here, maybe it will make things clearer.

It includes the opinion of Antirez, father of one of the most successful OSS ever: Redis. Maybe his words will open your eyes and tear the veil of Maya.

(spoiler ahead alert!)

Basically you work for free and people don't even thank you and the maintainer ends up being doxed or blamed or pushed aside and in the long term the only solution to keep sanity is to resign

https://www.jeffgeerling.com/blog/2022/burden-open-source-ma...

https://www.theregister.com/2022/01/13/opensource_apacheplc4...

https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-...

https://old.reddit.com/r/linux/comments/z14tt2/reason_why_op...

https://github.com/isaacs/github/issues/167

http://web.archive.org/web/20221217180915/http://antirez.com...

> But I don’t see how the GPL is a viable solution to that problem. Not at all

GPL doesn't permit freeloading, that's how

Do you wanna know who the freeloaders are?

Just make a list of companies that do not accept GPL code.

Those are the free loaders.

For people it's even simpler: you don't want to contribute to the project because it's GPL? then you are a freeloader.

Which is not the same of saying that if someone creates a project under Apache license he's a freeloader. There are many reasons to start a project under more permissive licenses, but if you plan to write something that has chances of being successful, think about what you're doing and who got your back.

It's one thing to create Go and make it opensource with Google backing you, another entirely to maintain log4j or GPG or OpenSSH on your free time for years or decades, without even a thank you and people constantly opening issue like "this thing is shit it should be rewritten in Rust" or "this project doesn't have a COC/ the COC is not inclusive enough I will blame you all over the internet" etc. etc.

My Apache/BSD projects are under that license because I know it's code that will be used in a context where GPL would not be accepted, but I also refuse to offer any kind of support whatsoever, basically once you get it, it's yours, I won't even close your issues, I will simply ignore them, that's how much I care about it.

Because I don't care to work on stuff that people are not forced to contribute back to, unless it's for myself.

Need a feature? Show me the money and I will think about implementing it.

> . Not at all. More likely, if I release my code under the GPL not only won’t I get paid, but also nobody will use my software

textbook straw man

you will get paid in code.

Linux is GPL, Vim is GPL, Emacs is GPL, GCC is GPL, Gnome is GPL, KDE is GPL, OpenJDK is GPL, Telegram is GPL, VLC is GPL, Blender is GPL, uBlock Origin is GPL, etc. etc. it's notorious that nobody uses them...