6 ms·
LLVM does seem to be explicitly designed from the start to be "industry"-worthy rather than just academic research, though. It was actually offered to GNU year
by mhh__ 6y ago
LLVM does seem to be explicitly designed from the start to be "industry"-worthy rather than just academic research, though.
It was actually offered to GNU years ago but (if I read the thread correctly) rms didn't get the email because of the unique way he does email.
It's a shame it's not under the GPL, you can already see a sign of the future (present?) in apple not upstreaming their backends.
- Mutjake 6y agoIf it was licensed under GPL, my bet is that Apple would not have adopted it at all.
- mhh__ 6y agoThat's entirely possible, but does it hurt their bottom line? They switched from GCC, because LLVM was available (to grow and eventually use). Their aversion to the GPL seems mostly cultural, which is interesting given that we skewer microsoft for their sins along those lines 20 years ago now.
- throw0101a 6y agoApple has an aversion to GPL 3 and not to GPL 2.x because of what 3 forces people to do. It's the same with FreeBSD: once libgcc_s went to 3 they could no longer use it. It's the same reason why bash and rsync have not been upgraded on macOS to newer versions: they also started using GPL3.
- akavel 6y agoHonestly curious what's the thing that "[GPLv]3 forces people to do" in context of those cases? IANAL but interested in perspective of choosing license for some of my current and future works
- badsectoracula 6y agoNot lock down people's devices basically. [L]GPLv3 requires that people are able to replace the [L]GPLv3'd binaries in their own devices if they want to (so they actually take advantage of the code being FLOSS instead of some nice theoretical novelty - ie. it is nice that my router uses Linux and find it amusing that it comes with the GPLv2 printed out, but what is the point if i can't open it up and fix/change some things that annoy me?). Apple wants to keep the devices they sell you under tight control, so [L]GPLv3 rubs them wrong. And so they avoid it. Related: https://en.wikipedia.org/wiki/Tivoization https://en.wikipedia.org/wiki/Tivoization It might also be about patents since IIRC [L]GPLv3 requires that if you use a [L]GPLv3'd program and that program infringes some of your patents then you are not allowed to sue others over their use of your patents in the same program.
- throw0101a 6y agoSee also "Why is FreeBSD deprecating GCC in favor of Clang/LLVM?": * https://unix.stackexchange.com/questions/49906/why-is-freebsd-deprecating-gcc-in-favor-of-clang-llvm https://unix.stackexchange.com/questions/49906/why-is-freebs... GPL3 is more restrictive than GPL2, which in turn is more restrictive than BSD/MIT, in the name of allowing other freedoms for end-users.
- akavel 6y agoThanks, this link seems quite comprehensive and the answer author tries to write in a neutral voice - appreciated!
- pjmlp 6y agoApple doesn't upstream of their changes already, hence why you have a specific Apple column on cppreference. https://en.cppreference.com/w/cpp/compiler_support https://en.cppreference.com/w/cpp/compiler_support And the bitcode used by Apple Store for application delivery isn't 100% like the LLVM bitcode.
- mhh__ 6y agoHence why I said it was a sign of the future rather than a prediction. It's not going to get any better for software freedom, especially as we move into the cloud. We live in a post-FSF world, I think people are taking for granted the bean counters playing nice with open source software.
- bjornjajayaja 6y agoWe need software that works on the client side sans internet connection. Devices are really powerful these days so it’s funny things move to the cloud. It’s funny I’ve been using cloud storage for the past several years but I wonder why I don’t just back up to external drive or two. The convenience doesn’t buy much. I think folks really buy into laziness and technology hype. But fundamentally not much had changed in the software space compared to 20 years ago.
- hated 6y agoYou already know why you don't do backups to a local hard drive. And you won't start doing it either. Don't kid yourself, cloud is convenience.
- FpUser 6y agoThis is what I do. All my staff is backed up onto hard drives. I also have offsite server which takes backups from those backups just in case.
- chongli 6y agoI still hold out hope that things will get better in the future. Eventually Moore’s law will truly end. We will have to stop once we run up against hard physical limitations. Why is this a reason for optimism? Because it shifts the outlet for innovation elsewhere. Costs of manufacturing will drop as competition in the fab space increases. I think RISC-V is a sign of things to come. There is great potential for open and amateur hardware.
- segfaultbuserr 6y ago>It was actually offered to GNU years ago but (if I read the thread correctly) rms didn't get the email because of the unique way he does email. Interesting anecdote. Do you have a source for that?
- throw0101a 6y agoPerhaps this? * https://gcc.gnu.org/legacy-ml/gcc/2005-11/msg00888.html https://gcc.gnu.org/legacy-ml/gcc/2005-11/msg00888.html
- segfaultbuserr 6y agoCan you elaborate it a bit? I didn't see anything that suggested "rms didn't get the email because of the unique way he does email."
- rrss 6y agoprobably based on this: https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00594.html https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00... I don't understand the bits about RMS' email configuration, but in that message in 2015 he indicated that he did not know about the offer in 2005 to give copyright of LLVM to the FSF.
- segfaultbuserr 6y agoThanks for the source.
- mhh__ 6y agoI don't, someone linked it to me on here a week ago so I'll try and dig it up. Apparently rms never saw the email because of his server arrangement?
- legulere 6y agoGCC would not have taken it anyway, they tried to prevent parts of GCC getting used independently or as a library to keep the lock-in to GNU, while the architecture of LLVM is of embeddable reusable libraries.