RE: https://genomic.social/@rastair/116260826067877345
Extremely proud to work on this! Challenging and fun
| Github | https://github.com/killercup |
| Blog | https://deterministic.space/ |
| Currently in | Gothenburg 🇸🇪 |
| Pronouns | he/him |
Pascal
@killercup
- 555 Followers
- 222 Following
- 307 Posts
I'm just here to write bad jokes. Find me as @killercup on other platforms.
rastair (news/updates)Release v2.1.0 out today 🎉
- GPU acceleration: double speed! 🏎️
- Single-ended library support: works with e.g. Ultima data
- BAM output: annotate reads with either MM or XM tags directly in your bam file
- Improved and expanded QC reports
- Various small bug-fixes and speed improvements
This is something I should write a blog post about as well… but for now, if you're curious, check out https://www.rastair.com and its repo where this is happening :)
Feels good to be working on a Rust tool where optimizing it actually makes a difference. Last week, I was working on one of the fastest tools in its category. Then I got tricked into optimizing it, made Claude write some compute shaders for me, got rid of more `memmove`s, and now I think I can run on laptop in 10min what last week ran for 2.5h on a server with 16 cores! #rustlang
Released v2.0.0! Key improvements:
- highly accurate ML-based SNP calling
- Methylation calling at de-novo CpGs formed by a SNP
- highly accurate ML-based SNP calling
- Methylation calling at de-novo CpGs formed by a SNP
In case anyone else needs to hear it: `Vec::with_capacity(user_input)` is probably a bad idea and will eat your RAM when you least expect it. At least put a `.min(reasonable_max)` on it. #rustlang
Mara BosI'm excited to share what I've been working on with @erikjee: RustNL's #rustlang Maintainers Fund!
Many people and companies contribute to Rust, but there are fewer and fewer paid positions for general maintenance (reviews,cleanups,etc). We need to fix that.
General maintenance is one of the most fundamental jobs in an open source project, but is one of the hardest to get paid for. Adding new features gets you promoted; keeping the lights on does not.
But everything depends on it. Code needs reviews, cleanups, docs. New contributors need mentors, etc.
A significant number of Rust maintainers who got paid for that have lost or quit their job recently. Due to RTO policies, a shift in responsibilities, budget cuts, and/or burnout. This is already quite noticable in the Rust project: longer review queues and more technical debt. This is a problem.
Through RustNL, the non-profit foundation behind the largest Rust conference (RustWeek) and the Rust Project's All Hands, we are setting up a fund to provide stable jobs for Rust maintainers. We want to employ six full-time maintainers in 2026.
Additionally, we'll provide internships and mentorship, to help retain promising new contributors. Not only do we need to make sure the current generation of maintainers doesn't burn out, we need to work on the next generation of maintainers too.
What we need now is companies who rely on Rust to step up and contribute financially. Having your business rely on the work of unpaid volunteers is not sustainable in the long term. It's a risk.
And if your company contributes to Rust, keeping the project well-maintained will accelerate your work.
Over the last few months, we have spoken to the Rust Foundation and several big companies about our plans. The input we've received and the positive reactions so far makes us believe we can make this happen. Today, we are publishing our plans for a wider audience, in search for the required funding.
If your company is interested in funding Rust maintainers, please reach out to me or @erikjee!
You can find our sponsors prospectus here: https://rustnl.org/resources/Rust-Maintainers-Fund.pdf
Let me know if you want to talk! 💛
(Message me through Mastodon, Rust Zulip, or email: [email protected])
At #EuroRust and picking the talks about stuff I would never look into otherwise :) cosmic was interesting and now learning about Petri nets
jan-erik