No copy-left license?
Compatibility on Linux with BSD-like operating systems such as FreeBSD, MacOS?
To annoy Richard Stallman?
No copy-left license?
Compatibility on Linux with BSD-like operating systems such as FreeBSD, MacOS?
To annoy Richard Stallman?
Are you planning to make proprietary changes to `cat` you are unwilling to share?
> Compatibility ...
GNU coreutils work fine on all the mentioned plattforms
> To annoy Richard Stallman?
Not really sure if pettiness would be sufficient motivation for me, but then again, I'm writing this response...
Presenting to you Panthera(TM) - the Enterprise Ready cat that you were waiting for!
* LDAP support
* Office 365 integration
* SAP integration
* GDPR compliant outputs
* 24/7 SLA
Plenty of GPL software is available on osx.
The decision is also affected by the Tivoization clause introduced to GPL v3.
> If MacOS included GPLv3 software, Apple wouldn't be able to pre-install it unless they provided all users with signing keys to install their own modified versions of the GPLv3 software on-target. Check out the GPLv3's "User Product" and "Installation Information" sections for more details - they're written in plain English, and are pretty clear. [2]
[0]: https://meta.ath0.com/2012/02/05/apples-great-gpl-purge/
But Apple holds lots of patents[1], and while it's hard for me to imagine Apple enforcing patents against users of bash, I can easily imagine Apple lawyers making a strong enough case to management that the potential value of all patent licenses that would be implicitly granted by GPL 3 was likely to exceed the cost of feature-freezing or replacing affected macOS components that they would have agreed to a blanket ban.
Note that I'm not defending this decision: for the record, I detest software patents, dislike tivoization, and the only problem I have with GPL 3 is when companies that might otherwise contribute to GPL 3 projects are uncomfortable with it. Which is unfortunate, but certainly not a flaw in the license itself.
[1] https://patents.google.com/?assignee=%22Apple+Inc%22&oq=assi...
And even then companies are famous for leeching on open source projects, with gpl you at least have some hope of companies leaving you alone or giving back something.
How is it "leeching" if I deliberately release my source code under a BSD license because I don't care if other people use it or not? It can't be "leeching" if I don't care about their contributions either. The only other scenario that would apply is if I wanted to be paid for my work... in which case neither a BSD-like license, nor the GPL, would be adequate.
This is the problem I have with GPL partisans: They refuse to accept that projects can be completed, or that anyone can have any interests other than GPL-compatible ones.
Monetization in FOSS is a systemic issue, with few exceptions, but even then you are far more likely that companies won't want to risk leeching with a GPL like license than a permissive one because of the code sharing requirement, which MIT/BSD at best only incentives as goodwill because of complexity maintaining the project they rely on.
I also find it funny you create a strawman, i never stated any adoration of GPL.
Especially when you make clear the option to dual license and let them use it under a MIT/BSD style license, or something custom, if they pay you an appropriate amount.
What downfall, exactly? If I want to get paid, the GPL doesn't help me with that. If I don't care about outside contributions, the GPL doesn't provide any advantage. Insofar as I have written something that is complete in itself then a BSD license makes perfect sense.
Meanwhile regular commits from / sponsored by Netflix, Dell-EMC Isilon, Juniper, Mellanox, Intel, Amazon and Microsoft (for network drivers), etc.
An absolute great OS?
>hardly any upstream contribution (Apple, Sony, etc)
Sony paid FreeBSD dev's, and the Apple kernel and coreutils are opensource, it's just they have not done anything FreeBSD is interested in, not like for example Netflix with in-kernel tls.
>At this rate BSDs will be deader than dead within a few years.
Yes yes you said that already 20 years ago, it's probably time to overthink it.