Depot becomes Biome's exclusive sponsor
As for today, we’re happy to announce that Depot has become Biome’s exclusive sponsor!
Biome by the numbers
Section titled “Biome by the numbers”Biome is a big Rust project, that keeps growing overtime. As for 17th of November (time of writing of the blog post), the project has the following stats:
- A total of 90 internal crates (AKA
biome_*crates) that are compiled and shipped in production. - ~651,971 lines of code between production code and test code.
- ~3,217 Rust files, between production code and test code.
Since Rust is a compiled language, with complex syntax, the resources required for compilation, testing, etc. are bound to increase over time. Before Depot came to the rescue, Biome used to use GitHub Action runners. Here’s a few numbers:
- Linting for pull requests took around ~15 minutes.
- Tests for pull requests took around ~20 minutes.
- Benchmarks for pull requests took around ~30 minutes. Benchmarks take longer because the code is compiled in production mode, and we make sure to stress test our infrastructure by feeding the benchmarks very complex inputs.
- A release might have required up to ~45 minutes.
- At some point, Biome on Windows couldn’t compile due to the memory required, which exceeded the memory available in the GitHub Actions runners.
Enters Depot
Section titled “Enters Depot”I discovered Depot by chance on social media. Someone thanked them for sponsoring their Rust project, so I reached out to see if they’d be willing to sponsor Biome. Jacob Gillespie, CTO and Co-Founder at Depot, was incredibly responsive and eager to support us.
Depot started sponsoring Biome’s GitHub infrastructure months ago as a gold sponsor. With their faster GitHub Actions runners, our workflows saw dramatic improvements:
| Workflow | Before (GitHub runners) | After (Depot) |
|---|---|---|
| Linting | ~15 minutes | ~2 minutes |
| Tests | ~20 minutes | ~4 minutes |
| Benchmarks | ~30 minutes | ~15 minutes |
| Releases | ~45 minutes | ~25 minutes |
Depot’s impact on the ecosystem
Section titled “Depot’s impact on the ecosystem”These aren’t just numbers. Having a faster CI has had a significant positive impact to maintainers, contributors and end-users.
Maintainers
Section titled “Maintainers”We’ve seen positive outcomes throughout the whole project management process. We’re able to get faster feedback from our CI jobs, release more frequently and with more confidence, and we can fix CI issues faster. As you know, CI is a YOLO practice!
Contributors
Section titled “Contributors”Contributors can see the effect of their PRs way faster than before, and fix possible bugs promptly. This means that by the time a maintainer comes and reviews the PR, it might be approved already because the CI is green! One reason why we’re able to ship so much fixes in every patch release.
End-users
Section titled “End-users”End-users - you, the developers - can enjoy that fix you needed sooner than before!
Depot’s endorsement
Section titled “Depot’s endorsement”Like Vercel, Depot believes that Biome’s inference engine can and will improve the developer experience even further.
Depot believes in Biome’s mission, a unified toolchain where users can think less about their tools and dependencies, and more about building their own software using modern practices.
Thank you, Depot!
I like where this is going, how can I help?
Section titled “I like where this is going, how can I help?”I want to remind you that Biome is a project led by volunteers who like programming, open-source, and embrace the Biome philosophy, so any help is welcome 😁
Translations
Section titled “Translations”If you are familiar with Biome and would like to contribute to its outreach, you can assist us by translating the website into your native language. In this dashboard, you can check the supported languages and if they are up to date.
Chat with us
Section titled “Chat with us”Join our Discord server, and engage with the community. Chatting with the community and being part of the community is a form of contribution.
Code contributions
Section titled “Code contributions”If you like the technical aspects of the project, and you want to make your way into the Rust language, or practice your knowledge around parsers, compilers, analysers, etc., Biome is the project that does for you!
There are numerous aspects to explore; I assure you that you won’t get bored. Here is a small list of the things you can start with:
- Create new lint rules! We have so many rules that we haven’t implemented yet (ESLint, ESLint plugins, Next.js, Solid, etc.). We have a very extensive technical guide.
- Help building Biome parsers! One interesting fact about Biome parsers is that they are recoverable parsers error resilient which emit a CST instead of a classic AST.
- Implement new capabilities in our LSP (Language Server Protocol), or add new features in one of our editor extensions: VS Code, Zed and JetBrains IntelliJ.
Financial help
Section titled “Financial help”If you believe in the future of the project, you can also help with a financial contribution, via Open Collective or GitHub Sponsors.
Additionally, the project provides an enterprise support program where a company you can employ one of the core contributors to work a specific aspect of the Biome toolchain.
Sponsored by
Copyright (c) 2023-present Biome Developers and Contributors.