5 ms·
I'm always confused by this stance. It presupposes that big companies like Apple and Google will at some point become bad actors in the opensource world. (They
by josephg 12y ago
I'm always confused by this stance. It presupposes that big companies like Apple and Google will at some point become bad actors in the opensource world. (They both contribute huge amounts of code). Even Microsoft is starting to open up their codebase with the release of huge parts of the .NET ecosystem.
Frankly, I want the big boys on my side when it comes to opensource code. I want them to use the code I write. Usually I indirectly benefit from them using my code anyway, and they benefit, and everyone's happy. This is true even if they decide to make proprietary changes which don't get pushed upstream. I gain influence in my community and lucrative job offers. I get invited to talk at tech conferences, and my projects (present and future) attract more attention. I honestly don't see the downside here.
Apple might have a change of leadership and decide to swim against the current and make LLVM proprietary, but if that happens can't we just fork it? As far as I can see, MariaDB is doing just fine. And until that happens (which will probably be never), we can get some huge compiler ecosystem improvements on Apple's dime. All opensource.
Am I missing something, or is this fear of corporations totally unjustified?
- davidw 12y ago> Am I missing something, or is this fear of corporations totally unjustified? Sun Microsystems basically grabbed BSD development by hiring up a lot of good people and running with it. It took a while for the various free BSD's to come into their own. Basically, with "bsd licensed" software, if a big company hired up all the developers, they could take it proprietary and out-compete fork efforts. I don't think it happens often, but it's not impossible, either.
- hga 12y agoReally??? The AT&T lawsuit and the end of DARPA BSD funding and that research group at UCB didn't have a lot to do with that? That was several years after Sun got in bed with AT&T and announced that BSD based SunOS was doomed. I don't know, but I wonder.
- davidw 12y agoThere are lots of factors, and you can't exactly rerun the experiment a number of times, tweaking all of them. There's also the fact that the internet was far less available in that day and age, making it more difficult to get good people involved. I don't think it's a big risk, but like I said, I don't think it's impossible either.
- dragonwriter 12y ago> Basically, with "bsd licensed" software, if a big company hired up all the developers, they could take it proprietary and out-compete fork efforts. Well, look, sure, if you hire all the developers that are working on something and understand it, you can probably out-compete other implementations even if all you have the old developers do on your proprietary project is write up specs from which a different set of developers build a legally non-derivative interoperable implementation. That may be a risk with permissively-licensed Free software, but its also a risk with copyleft Free software and proprietary software.
- davidw 12y agoMy experience is that specs - even will written ones - are far enough from working, tested code that it's going to be significantly easier to take the BSD project proprietary than to build a competitor to a GPL licensed one from scratch. Also, to be attractive to the 'core group', I think working on new stuff is more interesting.
- vetinari 12y agoThat pressupossition is not that unrealistic. For example, see shader compilers for GPUs. How many open shader compilers do you see around? Is there any motivation to open them? On the other side, during the 90's, we have seen many vendors come with new CPU ISAs, extensions of existing ISAs, new SOCs, etc. Many of them didn't have resources or will to write a new C compiler, so they wanted to use someting existing. They were willing to write new GCC backend - and GCC license basically forced them to be open. After this, there was no point in keeping ISA specification secret. LLVM/clang does not have this effect. It pretty much rewards for being closed. So today, we have shitty (especially on ARM-SoCs) shader compilers for secret ISAs, and you aren't going to see their sources anytime soon.
- j_s 12y agoI am not very familiar with the world of shader compilers, but it seems like you have provided the most concrete example I've heard yet of how GCC benefited in the long term in a way that LLVM/clang didn't. I would love to hear from anyone with more expertise in this realm who might be able to dispute this claim in any way... otherwise this seems to be a smoking gun in GCC's favor!
- pgeorgi 12y agoThere are some llvm based shader compilers out there. Some even open (AMD), some not (Nvidia). The situation with architectures in 90s sounds about right: Those that were kept closed (and where a gcc backend was thus no option for the vendor - mostly embedded stuff) have to this day shitty compilers with unpredictable optimizers.
- GalacticDomin8r 12y agoI'm not sure about the exact conclusion you seem to draw but it seems to be something like "GPL projects tend to have better outcomes than non-GPL". The whole point of the thread doesn't support that conclusion coming directly from the GCC brain trust. It's only natural that niche GCC users are going to hang around the longest. I'd also like to note LLVM/clang didn't gain large non-apple marketshare until GCC adopted GPLv3 which has more to with it's stagnation than anything IMO. v2 is palatable to many business needs, v3 is not.
- throwaway90999 12y agoMicrosoft is opening their codebase because they've been crushed by the enormous efforts of open source. This concession was hard won over the course of decades. Apple and Google do not contribute code freely, nor do they contribute a significant amount of their code. The contributions are limited to areas in which an advantage exists. One only has to look at the machinations present in other development platforms to realize the threat. Consider what's happened with Java in recent years. Or look to Swift. Or to the entire Microsoft ecosystem which was built in part on a foundation of open source. BSD licensed code permeates the Windows environment; to ask "what's the concern" belies a rather stunning ignorance of Microsoft's behavior over the three prior decades.
- hga 12y ago"because they've been crushed by the enormous efforts of open source" As opposed to their own ineptitude (e.g. Vista and Windows 8) or the changing of the guard from original founders? I'm certain open source played a role, but I suspect a secondary one. Heck, if post XP Windows didn't suck so much, I and my parents (who nowadays run what I build them) would be using it instead of Linux for our desktops.
- throwaway90999 12y agoVista and Windows 8 aren't the problem. Lack of presence on servers and mobile devices is the problem -- those are the two key spaces where OSS platforms have won out. Linux is still not a significant player on desktops. Microsoft is still completely dominating that space.
- hga 12y agoMobile devices I firmly ascribe to ineptitude, and can supply some 2nd and 3rd hand details I've read about. Servers are more complicated. In the mid-90s Windows NT started dropping in quality, and the much older decision to have mandatory file locking resulted in situations where creating a server with a major MS server application could require ~ 20 reboots. And many more bug and security fixes require reboots than they do on UNIX(TM) based/inspired platforms. Then one could argue ineptitude in marketing when Microsoft didn't cut deals that could have made their software competitive for mass installations. I really wonder about that, because so many of these need source, but it's "a path not traveled", except internally with Azure.
- fungos 12y agoNarrow and egocentric view of the situation. This is not about developer (your) freedom (to use, to change, to gain over) but is about user freedom. Do a little research about RMS's history and what he defends instead of just reading some (context) limited mailing postings to have your conclusions.
- CamperBob2 12y agoI'm always confused by this stance. It presupposes that big companies like Apple and Google will at some point become bad actors in the opensource world To resolve your confusion in this area, perhaps you should consult an Oracle.
- riffraff 12y agoaren't we in that world already? I.e. the swift compiler uses llvm but is not open source, the obj-c compiler used gcc and it was.