Actually, I was only meaning use it internally to improve their own workflow.

They can still bundle it with other things, only release your code, secretly improving only what they did on top of your API and make money out of the bundle, so why stoppping there and using a free license rather than something with a NC clause?

On the other hand, one could argue that GPL would refrain a corp from including your software in their product, while at least the cite you get with the MIT license at least gets you some advertisement and potential.

What if other free software developers use a license incompatible with the GPL for their own reason, is it OK to deprive them from the right to simply incorporate your code in the name of fighting big tech?

I don’t mean to say that it does not make sense to use the GPL, it is probably the most sensible choice if your aim is to fight big tech corporations. But not every piece of software is written as a commercial weapon.

Create a post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

  • 0 users online
  • 5 users / day
  • 20 users / week
  • 27 users / month
  • 16 users / 6 months
  • 20 subscribers
  • 684 Posts
  • 1.7K Comments
  • Modlog