Become a sponsor to LCrossman
LCrossman
🦠Hi, I'm building microBioRust – blazing-fast, eco-conscious bioinformatics tools focused on microbes. It is on the lines of Rust meets genomes, with less memory leaks and more metabolic pathways.
I’m bridging computer science, biology, and bioinformatics to create tools for the community, and with the community. From parsers to pipelines, I'm collaborate with amazing international developers and microbial bioinformaticians to make open science faster, more eco-friendly and slightly less painful.
Your sponsorship helps keep the bugs in the right places (genomes) and out of the code. I’m not funded elsewhere—just fuelled by science, community, and probably too much coffee.
Thanks for helping this project evolve! 🦠
If I had 25 monthly sponsors I would be able to: ☕ Drink coffee that isn’t labelled “For Research Use Only.” 🌍 Support more global contributors be they 🖥️ or 🦠, Add new features at the speed of a doubling E. coli and 🧬 Build smarter, faster, greener tools—minus the genome-sized burnout. Basically: fewer funding worries, more beautiful bugs (in genomes, not code), and more time building tools that help the bioinformatics community actually get things done.
Featured work
-
LCrossman/microBioRust
Rust bioinformatics crate aimed at Microbial genomics
Rust 18
0% towards 25 monthly sponsors goal
Be the first to sponsor this goal!
$5 a month
SelectTier 1: "Seedling support" 🧫
You provide the foundation for healthy cultures, both bacterial and open-source
perks: Listed in the README Petri dish hall of fame
$10 a month
SelectTier 2: Gene whisperer 🧬
You are reshaping biology, one codon at a time!
perks: A thank you in release notes and a warm digital thanks
$25 a month
SelectTier 3: Phylogenetic Champion 🌳
Like a robust tree, your support underpins everything!
Perks: Logo or name goes in my project README, prority bug fixes
$100 a month
SelectTier 4: Sustainable Science Steward 🌿
You are building open science that lasts and is green, ethical and maintained.
perks: Direct influence over the project direction, Logo in the project docs, and named shoutouts in a release you've influenced