Landing page
https://essence.handmade.network/
Screenshots
https://twitter.com/_nakst/status/1477247856805351425
We do not have a specific category for OS that dos not fit into Linux, Mac, Unix or Windows, so I posted it in here because I think that could be more interesting for Linux user.
Correct, but depending on the specific license, they would still have to distribute the source (read: not JUST credit you, THEY have to independently provide a way of getting access to the source code), and if they make any improvements, which they’ll probably want to do, they have to share that back with you. This results in the product itself continuously improving for everyone, profit or not.
If there wasn’t a license term against it, companies will be greatly incentivized to keep any improvements they made closed and therefore their product will be better than the original open source product, which will give their now proprietary product an edge in the market, which has historically shown to be enough to snuff out the original open source efforts.
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.