Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sold
-
This isn’t the way to speed up Rust compile times
It’s tentatively planned for 3.0. https://github.com/bluewhalesystems/sold/issues/8
The file formats are indeed totally different. But the operation of linking is the same at a high-level.
-
Apple Releases New Static Linker
...and the macos/iOS-supported version, sold, is commercial and non-AGPL.
see https://github.com/bluewhalesystems/sold
- sold: The commercial version of the mold linker
- Sold: The commercial version of the mold linker
-
The real answer
sold? (Yes I'm on macOS)
- Is Thread more expensive to manufacture than ZigBee and does Matter certification cost anything?
-
Mold Linker v1.9.0 release
mold/macOS is commercial software. For mold/macOS, please visit https://github.com/bluewhalesystems/sold. ```
-
Mold linker: targeting macOS now requires a commercial license
> Note that `sold` is still free-as-in-£ for use in CI/CD
The relevant part of the EULA [1] states:
> Individuals who use the Software only occasionally, or non-interactive use of the Software that is not explicitly invoked by an individual such as CI/CD (continuous integration/continuous delivery), are not considered Active Interactive-use Users ("AIUs"). No additional fees are required for such uses.
I had to read it multiple times to understand the CI/CD bit. It's not clear to me whether the EULA says that CI/CD is an example of "use that is explicitly invoked by an individual" or if it's an example of "non-interactive use that is not explicitly invoked by an individual" - the wording is unclear to me and can have either of the opposite interpretations.
At my day job, we occasionally test C++ code changes by compiling in a CI/CD system to obtain a container image that we can push into a staging environment. This means we have a develop-compile-test cycle where the "compile" step involves pushing to a merge request branch, waiting for CI/CD to finish, and then running a deploy script to push out the newly-built image for testing. I wonder if this would be considered "Active Interactive-use Use" or not.
[1] https://github.com/bluewhalesystems/sold/blob/main/LICENSE.m...
- Sold - the commercial version of Mold linker
- Sold: A commercial version of the mold linker
mold
-
I reduced (incremental) Rust compile times by up to 40%
I think this is unlikely to gain traction. I say that no to discourage you, just to explain.
- The community has an instinctive distrust of closed source or a compiler from an untrusted source. If you’re familiar with the Trusting Trust attack you’ll understand why.
- Dev tools in every language ecosystem are almost always free, unless they involve some kind of hosting. People aren’t used to opening their wallets. Look the experience of the guy who built the mold linker(https://github.com/rui314/mold). Far superior to the state of art, improves incremental compiles a lot, widely applicable across ecosystems (C, C++, Rust), CPU architectures and Operating Systems. You don’t even have to modify your compiler, just need to point to his linker. He’s even giving it away for free for personal use. But still, almost no one uses it. The inertia of the established options is really high.
- It’s not complex enough. Think about the complexity involved in the cranelift backend. No one can seriously recreate the efforts of bjorn3. If we could have, we would have. But the idea idea here can be recreated, especially by the experts who already built incremental compilation into rustc.
- But if your solution is truly complex, like the parallel frontend, the burden of maintaining a fork would be too high. You’d have to spend all your time rebasing.
Again I’m not trying to discourage you, just stating the difficulties of making a business in the dev tools space. You would be better off contributing this excellent work to the community and trying a different tack.
-
Mold Course
I initially thought this would be about the mold linker (https://github.com/rui314/mold)
-
Monetizing Developer Tools
I assume this submission is trying to highlight the specific message (2023-01-24) : https://github.com/rui314/mold/issues/190#issuecomment-14028...
Fyi... the author wrote a more expansive blog post about selling dev tools a few months later (2023-06-06) and there was a related HN thread about it: https://news.ycombinator.com/item?id=36225016
-
mold 2.1.0 - rui314/mold
Loongson's LoongArch CPU has been supported. (03b1a1c)
-
Mold 2.0.0
I'm amazed at how quickly the author responds to requests: https://github.com/rui314/mold/issues/1057
From the report to the fix in less than two days.
I'm not sure how competitive it will be with lld, especially if we consider ThinLTO (which takes multiple minutes on 64-core machine) - it can make the advantages of mold insignificant.
- Mold 2.0 released - MIT license
-
Linking many files significantly increases build time. Is there an editor that allows you to write a single file but present the file to the screen as multiple 'virtual' files for better organization?
What other solutions have you tried for the problem of slow linking? You haven't even said which linker and what flags you're using. I haven't actually tried it, but the author of gold has an even faster linker called mold: https://github.com/rui314/mold
- Design and Implementation of the Mold Linker
-
Apple's new library format combines the best of dynamic and static
> Mold did it first, though: https://github.com/rui314/mold
Before LLD?
What are some alternatives?
xi-mac - The xi-editor mac frontend.
zld - A faster version of Apple's linker
wasmtime - A fast and secure runtime for WebAssembly
osxcross - Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
chibicc - A small C compiler
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
gccrs - GCC Front-End for Rust
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
bevy - A refreshingly simple data-driven game engine built in Rust
tonic - A native gRPC client & server implementation with async/await support.
llfio - P1031 low level file i/o and filesystem library for the C++ standard