←back to thread

Wild – A fast linker for Linux

(github.com)
383 points hkalbasi | 3 comments | 24 Jan 25 16:25 UTC | HN request time: 0.004s | source
Show context
pzmarzly ◴[24 Jan 25 16:55 UTC] 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 ◴[25 Jan 25 03:05 UTC] No.42819089[source]▶
Why does AGPL Vs MIT matter for a linker?
replies(4): >>42819229 #>>42819957 #>>42820650 #>>42821513 #
zelcon ◴[25 Jan 25 03:32 UTC] 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 #
pwdisswordfishz ◴[25 Jan 25 07:39 UTC] No.42820180[source]▶
They don't have to release source for internal forks.
replies(1): >>42821477 #
wyldfire ◴[25 Jan 25 13:18 UTC] No.42821477[source]▶
They do if they're AGPL licensed and the internal form software is used to provide a user facing service.
replies(1): >>42838250 #
1. amszmidt ◴[27 Jan 25 07:15 UTC] No.42838250[source]▶
But then it isn’t “internal”…
replies(1): >>42861990 #
2. zelcon ◴[29 Jan 25 05:55 UTC] No.42861990[source]▶
It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL.
replies(1): >>42916626 #
3. amszmidt ◴[03 Feb 25 09:52 UTC] No.42916626[source]▶
The effort involved, and legal risk is exactly the same as for any Copyleft license. If you don't know what your stack is doing, that is the problem -- not the license.