4 ms·
We are currently on Buildjet and it has made significant difference for our rust builds. But I would change in a heartbeat for Windows and even more for MacOS s
by Sytten 3y ago
We are currently on Buildjet and it has made significant difference for our rust builds. But I would change in a heartbeat for Windows and even more for MacOS support. Mind you only if it is per minute pricing. The GitHub Actions macos machines are sooo bad that anything else at this point I will take.
- suryao 3y agoWe have a few users who were using BuildJet try us out and they like it. It's an easy switch if you want to check it out.
- shepherdjerred 3y agoWhat do you need macOS for? Have you considered cross-compilation? Zig + Rust allows cross-compilation for Rust: https://actually.fyi/posts/zig-makes-rust-cross-compilation-just-work/ https://actually.fyi/posts/zig-makes-rust-cross-compilation-...
- mratsim 3y agoAnything that interact with the kernel needs to be tested on the actual OS. Simiarly if you call native libraries. And Apple Clang masquerading as GCC or not having all upstream LLVM patches is also annoying.
- shepherdjerred 3y agoSure, but now your interaction with macOS is limited to automated testing and not compilation + testing. Depending on the application, this could be worthwhile. For example, at work, we cross-compile C/C++/Fortran/Rust code in R packages. We compile for supported versions of R, so that ends up being tens of thousands of packages that we need to compile. By cross-compiling we saved a lot of work and nearly eliminated our need for macOS.
- suryao 3y agoA very common use case for macos runners is iOS builds.
- shepherdjerred 3y agoYou can cross-compile iOS apps.