95
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Mar 2026
95 points (99.0% liked)
Technology
42081 readers
219 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 6 years ago
MODERATORS
This one is so stupid, I had to think how to respond.
Why? What prevents anybody to implement a new Compiler, looking at LLVM ... ?
What we would have are closed source gcc forks, that is not freedom. This is the opposite.
I am old enough to remember buying a fucking Borland license
I work on gcc code, I know how ugly, historic in parts and confusing the Codebase can be. But I also know why. LLVM has no such legacy, and this is a good thing. I believe some day LLVM will replace gcc because of that. And LLVM uses Apache 2.0.
So, what exactly was your argument here?
Duno, you tried to convince me that the xGPL restrictions are only for my benefit. I strongly disagree with that opinion, that's all. And I do not really care about argument, if something is used more often, then it's best suited for me. I avoid to contribute to GPL projects and prefer some with MIT or BSD licenses.