7 ms·
The sad thing is that "easy to link and embed" and "permissive license" really didn't have to go together like they did in LLVM. GCC could have provided a libr
by JoshTriplett 11y ago
The sad thing is that "easy to link and embed" and "permissive license" really didn't have to go together like they did in LLVM.
GCC could have provided a library that made it easy to do code generation or compiler development. That library could still have used the GPL, so that only Free Software could use it. Some of the work that has happened around LLVM wouldn't have happened around such a library, but some of it would have. (GCC has much more recently started down the "plugin" route, but too little too late.)
For instance, Swift might not have happened. But Rust may well have; a rustc compiler under GPL would not have broken anyone's ability to use it, any more than GCC's GPL prevents people from building proprietary software with it.
But instead, the GNU project chose to make it difficult to build any extension to GCC outside of GCC's own codebase. So instead of having an easy-to-use library provided by GCC under GPL, which might have furthered many of the GNU project's goals and encouraged more Free Software compiler development, they forced the development of an entirely separate compiler project to provide such a library. And the people who came along to do so, since they had to rewrite it anyway, chose to do so under a permissive license.
So, at least in hindsight, the Free Software world is worse off than it would have been had GCC provided a library infrastructure.
- the_mitsuhiko 11y agoI doubt that rust would have happened under the gpl but i would love to hear what the rust team has to say about that.
- pcwalton 11y agoI personally see no reason why the GPL would have been a blocker to Rust. But I'm glad for the permissive license.
- kibwen 11y agoThe Rust team knew from the outset that repurposing a C++ backend was the only pragmatic way to compete with C++ on performance given their manpower constraints and projected timeframe. Even if all available backends had required the use of GPL, Rust would have still chosen one and moved forward with it. Fortunately, given that Graydon did prefer a permissive license for the compiler, LLVM provided exactly what he was looking for.
- raverbashing 11y agoOr they would just translate Rust to C++ Might be hard at first and not very compatible with different compilers, but it is doable
- djsumdog 11y agoI feel like you're missing the point of the GNU GPL. The original idea behind the FSFs idea of open source was an ecosystem where every new development resulted in more open and free code. We're talking about people who truly believed in getting away from commercial software entirely. There were people who felt that one day, Linux desktops could replace Windows and even high end tools like Photoshop and Final Cut would have great open source replacements. ...but that never happened. Apple has tried to remove all GPL code from Mac OS. Where GPL code exists, it's only GPLv2 (like Bash; using an ancient version). Even though all these companies are embracing opens source, they're embracing only permissive licenses. They're open sourcing the underlying tech stack while keeping all their offerings closed. If you're on Android, you are totally locked into Google services. I've met people who tried only using F-droid and running "open source phones" (minus the drivers of course). Their phones sucked. One of them switched back because she was tired of writing apps to do things she use to be able to do with the Play Store. The dream of a GPL world where the software is free and you only pay for the hardware, is pretty much gone. We don't have federated systems, and where we do, no one uses them (GNU Social, Miro, Diasporia). This isn't the open source world some of us envisioned back in the late 90s. I personally, will keep as much of my code under GNU GPL as I can.
- jevinskie 11y agoYou would have ended up with GPL shims that read/write the IR from/to the disk and a closed source program that transforms the IR on disk.
- dman 11y agoThe FSF ideology was born at a time where the level of bidirectional mistrust between closed source software vendors and open source advocates was a lot higher than it is currently. The world has evolved since then and the business world now embraces open source, possibly for reasons that have nothing to do with ideology (shared r&d costs, commoditising lower layers of the stack and the realization that you can just as easily get lock in with open source software as you can with closed source). In a world where even Microsoft is releasing more and more of its crown jewels as open source every given week, the FSF position can appear out of place but this I think is a testament of how far we have come on the original goals of the project.
- pekk 11y agoThe dangers that befell things like the Gosling Emacs code, which informed GPL and FSF, haven't gone away. Companies like Apple are actively working to erode any progress that has been made on this front because of their intense levels of investment in proprietary lockin.
- dman 11y agoIndeed. Eternal vigilance is the price of liberty.
- spiralpolitik 11y agoYes they were so actively working to erode progress that they offered to license LLVM under the GPL. But because RMS uses an e-mail client written in the last century he missed the offer. https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00594.html https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00...
- hahainternet 11y agoThere's no offer there. Please don't dishonestly quote.
- sandGorgon 11y agoWhat GCC and RMS did (and I suspect their goal was all along) was to change the Overton Window [1] of acceptability for open source. Remember this was still the time that Solaris was not open source, and Microsoft was borging competitors . It was not definitely the Visual-Studio-is-open-source time. By creating a hard line, and building a compelling alternative to proprietary compilers, he introduced a seed of change in the minds of young programmers at that time .... All of whom are senior management now and share a belief that things like Protocol Buffers should be open source. In fact, its interesting that Android is inducing this change all over again (not Linux). Its a viable answer to "its not as good as an iPhone,why should I buy it". [1] https://en.m.wikipedia.org/wiki/Overton_window https://en.m.wikipedia.org/wiki/Overton_window
- SFjulie1 11y agoThe true genious is bill gates who invented closed source software in 1976 letter to the hobbyist. Now everybody cannot think of sofware as naturally different than propietary. Hence giving an opportunity for a natural monopoly. Bill gates used security an argument a lot, and only became a little more secure by using permissive open source or buying software from poorer concurrent that had no good backup from their banks. Bill gates is the baron de Beaumarchais of computers : whining about being riped of software he did not created because people would give the interpreter so that their code could be used. A right on the second creation. Just for the record Beaumarchais, whining for special treatment as an artist. He was a smuggler, a weapon dealer, a baron, an aristocrat, and a revolutionary AND he created the fundamental rights of authors. The true fundation of liberalism: as long as it works for me, let's do revolution.