This is a very incorrect association to make, as the existence of iOS has very little effect on the relevance of BSD. (Besides, Netcraft confirmed *BSD was dying long before iOS came out. :)
Sure, from the perspective of 20-30 years ago, there were dozens of proprietary forks of BSD Unix (including NextStep), and BSD looked like a lousy choice for open source distribution.
However that doesn't acknowledge the profound change internet distribution has had on how developers consume open source code. There is now a massive ecosystem of BSD/MIT/Apache licensed code and very few evil corporations sucking it up and turning it proprietary. (Much of this 'framework' code which was always problematic under GPL.) So we should acknowledge that BSD-style licenses are successful in their own right, and not keep relying on outdated FUD about Microsoft or Apple "stealing" code twenty-five years ago, because it largely is no longer happening.
Certainly Mac OS X has more relevance to the traditional BSD userbase than iOS, but that's because iOS preempted the existence of a mobile BSD userbase. Linux has not only Android but also a slew of smaller players like FirefoxOS and Tizen. BSD has nothing. It's hard to have less relevance than non-existence.
> (Besides, Netcraft confirmed * BSD was dying long before iOS came out. :)
Of course it was -- it has been under the BSD license the whole time and before Apple it was Sun et al as you note.
> However that doesn't acknowledge the profound change internet distribution has had on how developers consume open source code. There is now a massive ecosystem of BSD/MIT/Apache licensed code and very few evil corporations sucking it up and turning it proprietary.
That is almost a self-refuting statement. The primary reason to want a permissive license over the GPL is to use the code in proprietary software. In some cases that does result in the proprietary software dominating the open source equivalent in the market (as with OS X or Safari/Chrome), and the remaining cases (the framework code you mentioned) are the exact use case for the LGPL, which allows the framework to be used in proprietary software without allowing the framework itself to be supplanted by a proprietary fork.
It's completely ridiculous to claim there anything like a "mobile BSD userbase", and zero arguments beyond that were given. There's no real reason why Android or any other mobile OS couldn't be based on a BSD. Given the IP constraints of mobile phones, it probably would be a better choice than a bastardized Linux.
Oh, and "*BSD is dying" is a troll. HAND.
> The primary reason to want a permissive license over the GPL is to use the code in proprietary software.
The facts are that other than primordial forks of BSD Unix (e.g. iOS), 99% of the permissive ecosystem remains non-proprietary.
It's not like people are coding against "Ruby on Rails Professional" or "Angular.js Enterprise-Edition", all of this software is open and commoditized and free, and always will be.
> exact use case for the LGPL
I don't understand why BSD-style is much more popular than LGPL for 'frameworks'. Perhaps because it's because it's the "Lesser" GPL and the first link on the page is "Why you shouldn't use [this]".[1]
In the software industry, the FSF actually has a lot of moral authority. My guess is that if it doesn't look like they'll stand behind the LGPL, why bother?
The license is a success in the sense that the code is being used, but it's failed to protect the project/brand from a situation where their code is being used worldwide without anybody realizing it.
(In fact the biggest misconception seem to be that Apple is using vanilla BSD or FreeBSD, when it's actually based on CMU Mach/BSD.)
> Darwin 1.4.1 is the UNIX-based, open-source foundation of Mac OS X. It is based on FreeBSD and Mach 3.0 technologies and provides protected memory and pre-emptive multitasking. This release corresponds to the release of Mac OS X 10.1. https://support.apple.com/kb/TA25634?locale=en_US
.
> The BSD portion of the OS X kernel is derived primarily from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features. https://developer.apple.com/library/mac/documentation/Darwin...
I don't agree that 'the people that matter know' is necessarily accurate, I also don't think it's sufficient. FreeBSD depends on donations and people donate for a mix of reasons. For example you can successfully brag about donating to "Linux" because even in non-tech circles people know Linux is cool. But even in tech circles people don't know much about FreeBSD.
Not that donations as a from of conspicuous social responsibility makes sense from a rational point of view, but we're humans and there are many situations where we spend money just so people see us do it.
Keep in mind that both BSD Unix and CMU/Mach were funded by the government in order to advance the state of the domestic computer industry. In terms of successful government research projects, these two would have near top of the list!
That being said, it would be great if "FreeBSD" had a bigger brand (and perhaps wasn't seen as Apple's vassal.) But I think that has more to do with the fact that Linux effectively beat them to market versus any license logic.
Not that I care, as I don't have any issues with commercial code, but it is a good example of basing work on BSD licenses without giving it back.
I'd actually use Sun and BSD as an example, but yeah, it is a possibility, which is why I am not some kind of anti-GPL zealot. I think it's less likely these days, because the effort required to really run away with a big project is considerable.
Is it? Obviously the proprietary version has to be enough better to make a difference, but it still actually happens. Look at Konquerer. KHTML was LGPL, so Apple and Google have to release their changes to the engine itself, but not GPL, so Safari and Chrome are proprietary and nobody has even heard of Konquerer.
You're making a baseless assertion. Apple ships an enormous amount of GPL software with OS X. It makes no sense for them to write an entire browser from scratch just to avoid the GPL when they're perfectly happy shipping bash, emacs, samba, etc.
Is it? The Android userland isn't GPL'd at all -- I think the last GPL bit left when they switched from BlueZ to BlueDroid. I don't see any evidence as to why the GPL code in the kernel compels Google to release the Android userland in the Apache license, rather than keeping it closed-source.
It depends on the size of the contribution. If they only fix a small bug then there is no real reason not to contribute the fix.
The trouble comes when a company makes any kind of nontrivial improvement at all. In that case the proprietary version is significantly better than the BSD licensed version and any improvements made to the BSD licensed version can still be incorporated into the proprietary version but not vice versa, so the proprietary version will always be better and continue to gain users at the expense of the BSD licensed version.
Probably the most extreme example of this is iOS. Apple put a slick UI on BSD and now it runs on a billion zero-freedom devices while BSD is slowly dying. Compare this with Linux, which is much more popular in its own right and even more so if you include Android, which itself is much freer than iOS in no small part because the kernel is GPL'd.
The same thing can happen with any BSD licensed software. Anyone can do 25% of the work to create a proprietary version which is 25% better than the original and use it to cart off with most of the original's user base.
Ironically this is one of the things the BSD people complain about: Anyone can take software released under a GPL-compatible version of the BSD license, make some nontrivial improvements to it and release it under the GPL.