←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 #
secondcoming ◴[] No.42815102[source]
Maybe I'm holding it wrong, but mold isn't faster at all if you're using LTO, which you probably should be.
replies(6): >>42815189 #>>42815221 #>>42815904 #>>42816102 #>>42816403 #>>42840365 #
Arelius ◴[] No.42816102[source]
Yeah, if you're development process requires LTO you may be holding it wrong....

Specifically, if LTO is so important that you need to be using it during development, you likely have a very exceptional case, or you have some big architectural issues that are causing much larger performance regressions then they should be.

replies(4): >>42816339 #>>42816648 #>>42823665 #>>42824951 #
1. benatkin ◴[] No.42816339{3}[source]
Being able to choose a middle ground between development/debug builds and production builds is becoming increasingly important. This is especially true when developing in the browser, when often something appears to be slow in development mode but is fine in production mode.

WebAssembly and lightweight MicroVMs are enabling FaaS with real time code generation but the build toolchain makes it less appealing, when you don't want it to take half a minute to build or to be slow.