←back to thread

383 points hkalbasi | 1 comments | | HN request time: 0s | source
Show context
pzmarzly ◴[] No.42815005[source]
Ever since mold relicensed from AGPL to MIT (as part of mold 2.0 release), the worldwide need for making another fast linker has been greatly reduced, so I wasn't expecting a project like this to appear. And definitely wasn't expecting it to already be 2x faster than mold in some cases. Will keep an eye on this project to see how it evolves, best of luck to the author.
replies(5): >>42815102 #>>42815606 #>>42816517 #>>42819089 #>>42819826 #
panzi ◴[] No.42819089[source]
Why does AGPL Vs MIT matter for a linker?
replies(4): >>42819229 #>>42819957 #>>42820650 #>>42821513 #
zelcon ◴[] No.42819229[source]
Corps don't want to have to release the source code for their internal forks. They could also potentially be sued for everything they link using it because the linked binaries could be "derivative works" according to a judge who doesn't know anything.
replies(2): >>42819466 #>>42820180 #
saagarjha ◴[] No.42819466[source]
I think you should get new lawyers if this is their understanding of how software licenses work.
replies(2): >>42819928 #>>42825830 #
mgsloan2 ◴[] No.42819928{3}[source]
See for example https://opensource.google/documentation/reference/using/agpl...

> Code licensed under the GNU Affero General Public License (AGPL) MUST NOT be used at Google.

replies(1): >>42819962 #
jenadine ◴[] No.42819962{4}[source]
It’s their loss
replies(1): >>42820578 #
Defletter ◴[] No.42820578{5}[source]
Is it? Because open source tools re-licensing themselves to be more permissive would seem to indicate whose loss it really is.
replies(2): >>42820844 #>>42823838 #
1. michaelmrose ◴[] No.42823838{6}[source]
This might indicate moreso that they believe they won't lose anything by the transition and users might ultimately benefit