How to make Firefox builds 17% faster
mbitsnbites
159 points
28 comments
April 13, 2026
Related Discussions
Found 5 related stories in 61.5ms across 4,562 title embeddings via pgvector HNSW
- Hardening Firefox with Anthropic's Red Team todsacerdoti · 539 pts · March 06, 2026 · 55% similar
- 10% of Firefox crashes are caused by bitflips marvinborner · 65 pts · March 04, 2026 · 52% similar
- Partnering with Mozilla to improve Firefox's security meetpateltech · 19 pts · March 06, 2026 · 50% similar
- Claude Code told me what tools it needs to work faster chtefi · 25 pts · March 05, 2026 · 49% similar
- Making Firefox's right-click not suck with about:config mmsc · 284 pts · March 04, 2026 · 49% similar
Discussion Highlights (6 comments)
Devorlon
Why compile code when ccache faster
K0IN
wow, 17% is impressive with such an easy fix. i wonder if we could just build this as a separate project and pull the webidl files as a dependency.
shevy-java
So ... perhaps Mozilla should focus on user share dropping. I understand that speed is relevant, but focusing on that strategy does not really work when dinosaur-like extinction is around the corner.
mmastrac
Can you (err... buildcache) cache Rust proc-macros? I've been battling this with sccache and I'm now maintaining a 10-patch deep stack for the next.js build CI. Windows builds were ridiculously poor on cache hits rates too because of non-determinism that was not able to figure out. I'd be happy to test it out.
allenrb
I guess “purge 17% of the code” is not the correct answer?
evmar
I’m not too familiar with Firefox builds. Why are clobber builds common? At first glance it seems weird to add a cache around your build system vs fixing your build system.