Replies (1)

• @badmin@lemmy.today 2026-10-26 18:43

  Good list, since the three projects use public runners people can check. Tauri They must be cheating building from scratch (including fetching dependencies from crates.io) in github actions in <2 minutes and never freezing, despite those runners gaining a bad reputation lately. Servo The github runners building it in 4 minutes without freezing must be fake. Or maybe you were building SpiderMonkey from source, and that part was the problem 🙂 Gram If you mean the Zed fork, they must be cheating building from scratch (including fetching dependencies from multiple locations and repos) in <18 minutes (the total run includes running tests) in resource-limited codeberg runners, and never freezing. I also built this locally, and despite this being a wild project, and resource limiting the build on a workstation with a ~10 year old CPU, it finished in <24 minutes, and the target dir size (the build dir for those not familiar) is a WOPPING 3GiB (the executable alone is ~220MiB, ~168MiB if you strip it).

  Open ##5259189