(no title)
Arcuru | 2 months ago
If you want to use something, and your company makes $240,000,000 in annual revenue, you should probably pay for it.
Arcuru | 2 months ago
If you want to use something, and your company makes $240,000,000 in annual revenue, you should probably pay for it.
badsectoracula|2 months ago
I do not mind having a license like that, my gripe is with using the terms "permissive" and "open source" like that because such use dilutes them. I cannot think of any reason to do that aside from trying to dilute the term (especially when some laws, like the EU AI Act, are less restrictive when it comes to open source AIs specifically).
kouteiheika|2 months ago
Good. In this case, let it be diluted! These extra "restrictions" don't affect normal people at all, and won't even affect any small/medium businesses. I couldn't care less that the term is "diluted" and that makes it harder for those poor, poor megacorporations. They swim in money already, they can deal with it.
We can discuss the exact threshold, but as long as these "restrictions" are so extreme that they only affect huge megacorporations, this is still "permissive" in my book. I will gladly die on this hill.
whimsicalism|2 months ago
joseda-hg|2 months ago
Whatever name they come up with for a new license will be less useful, because I'll have to figure out that this is what that is
fastball|2 months ago
And honestly it wasn't a good hill to begin with: if what you are talking about is the license, call it "open license". The source code is out in the open, so it is "open source". This is why the purists have lost ground to practical usage.
jrm4|2 months ago
"Open Source" is nebulous. It reasonably works here, for better or worse.