|
Agree to disagree then. The alternative to Windows and OS X is not GPL-licensed Windows and GPL-licensed OS X, it's no Windows and no OS X, and we still have BSDs, Linux, and other open source systems in the ecosystem. Nobody who wants an open source OS has been restricted, and those who want a different experience than open source provides have the freedom to choose a proprietary OS. If someone wants an open source Windows or OS X they can make one[1][2]. They are not restricted. In the real world where not everyone is a programmer people don't feel restricted by proprietary software. Only in some hypothetical ivory tower manned by RMS are non-developers restricted by proprietary things. [1] http://etoileos.com/
[2] http://www.reactos.org/en/index.html I'm equally baffled when people can't accept a world where there is more than one type of license and software. Open source has its place in kernels, dev tools (editors, compilers, etc), education, and so on. That does not mean it's unequivocally the best and only model for all software in the world. I felt empowered after switching from Linux to OS X and I'm a developer, because I'd rather not hack on my OS to make it usable. I'd rather hack on the cool stuff that I want to hack on. I'd rather just use iPhoto than try to make F-spot, or whatever the photo app of the day on Linux is, not crash when importing photos, or upload to my online gallery, or usable for day to day use. I'd rather just use Billings than try to build my own open source version from scratch, presumably while still trying to pay the bills with other work. I'd rather just use Acorn than wait for GIMP to be usable by version 3.2 in 2020. And so on. I still use open source software too. Emacs, iTerm2, v8, Firefox, WebKit, Ruby, GCC, LLVM, and many small projects. And contribute to other smaller projects that I'm actually capable of understanding and contributing to such as node, GitX, and many libraries around the net. I open source tools that I make that I think others might find useful, and if someone takes my MIT licensed tool and uses it in a proprietary thing I think it's great that my code was able to help someone else. I don't selfishly demand that they contribute everything they add back to me if they don't want to. My code helped someone accomplish their goal faster or better and that makes me happy. If you don't understand that's fine, but I am absolutely not restricted by the proprietary software that I choose to use. I won't even call you narrow or selfish for not understanding. edit: While writing that list of open source software I use, I realized that only Emacs and GCC are GPL. Why is it that the most popular open source software is not GPL licensed? If the GPL encourages and fosters collaboration why is the MIT, BSD, and MPL licensed software more active and popular? It almost seems as if removing the restrictions from the GPL encourages collaboration. The Linux kernel is a notable exception, so I'm not saying this is 100% true, but the evidence seems to support it in many cases. |
This is irrespective and has nothing to do with the point. I can figure out tons of adjectives to """describe""" you. Also, I don't know why people think their reality is "the real world" and extrapolates it to others' "real worlds".
It is not about being a dev or not, it's about a system which someone relies on (even a society with Google) and ensuring its continuity and the best for all. If you ensure it, people will recognize your work and the money will come.
> While writing that list of open source software I use, I realized that only Emacs and GCC are GPL. Why is it that the most popular open source software is not GPL licensed? If the GPL encourages and fosters collaboration why is the MIT, BSD, and MPL licensed software more active and popular? It almost seems as if removing the restrictions from the GPL encourages collaboration. The Linux kernel is a notable exception, so I'm not saying this is 100% true, but the evidence seems to support it in many cases.
A software is "good" independent of its license. Licenses don't fix bugs. If you measure by adoption, then you should conclude that Visual Studio is what has encouraged most of the software developing in the past - and I think it's true, but hasn't to do with licensing and business models.
Your evidence supports that many licenses are being used, and that's a good thing. If you want to do things because many people does them, then you should adopt the Chinese culture. We have a phrase here: "Eat Shit: Trillions of flies can't be wrong." (this is not about Chinesse culture, they have outstanding good things and others not so good).
It took about 10 years to the industry to understand that they could earn money with open source software. It was very hard to try to explain someone that he could do better with a different model. Now that the industry has "internalize" it, everybody loves open source. AGPL is the next step: there is room for improvement and you will probably (IMO) do better with a more sustainable model.