RE: https://fosstodon.org/@mainmatter/117241212710498594
check it out friends! were getting started on the next chapter too!!
RE: https://fosstodon.org/@mainmatter/117241212710498594
check it out friends! were getting started on the next chapter too!!
another full @mainmatter workshop!! very exciting
ppl at @rustconf seem to be really interested in migrating codebases to Rust!
RE: https://fosstodon.org/@mainmatter/117230221469326597
come say hi if you’re around!!
Did you know C's int isn't actually guaranteed to be Rust's i32?
They line up almost always, except on niche architectures. Rust decided that "almost" is close enough. Read about what this means in our free C-to-Rust migration course: https://mainmatter.com/c-to-rust-migration-book/
rare PSA: we @mainmatter have our Rust engineers free right now! A client paused on budget timing, so they are coming straight off a highly complex c2rust project!
some of theee best engineers I know, looking for the gnarliest problems you’ve got! 👀
DM me if your company has those!
If you have a complex Rust project in front of you that you can't take on yourself, reach out here or at info@mainmatter.com!
3/3
. @mainmatter has an all-star Rust team available immediately.
After some budget hiccups at one of our clients, we happen to have a well-established team of Rust experts around that's ready to go immediately.
1/🧵
rare PSA: we @mainmatter have our Rust engineers free right now! A client paused on budget timing, so they are coming straight off a highly complex c2rust project!
some of theee best engineers I know, looking for the gnarliest problems you’ve got! 👀
DM me if your company has those!
RE: https://fosstodon.org/@mainmatter/117189845263518871
this is your once in a lifetime chance to ask us all your weirdest questions! dont miss it!
Our @unsafe and @algo_luca will be at @rustconf. Jonas will talk about learnings from our work migrating RediSearch from C to Rust. Luca will hold a workshop on C to Rust migrations, beyond the basics. See you in Montreal! 👋
Get your ticket 👉 https://rustconf.com/
I was asked recently about the cost of running a (#rustlang) conference and why the ticket prices are what they are. We figured we can just publicly share the numbers for RustWeek, in the name of #transparency. :)
RustWeek has many subevents (conference, hackathon, unconference, workshops, Rust All Hands, etc.), but I've tried to extract just the two day conference part of RustWeek 2026:
Venue rent: € ~50k
Lunch, snacks, drinks two full days: € ~130k (incl. catering services and exclusive access to 1000 person restaurant all day)
A/V services: € ~30k (incl. livestreaming, professionals operating the cameras/microphones/screens in the rooms, editing the recordings, etc.)
Stuff we set up at the venue: € ~20k (sponsor booths, entertainment, banners, stickers, wifi, etc.)
Travel compenstation for speakers: € ~10k
External services: € ~25k (accounting, registration & payment, event management, insurance, etc.)
Miscelaneous: € ~15k
This adds up to roughly € 280k for just the two conference days. (The total for all of RustWeek is ~€ 400k.)
The money we get from sponsors covers roughly half of the costs. The other half has to be covered by tickets.
We are currently the biggest Rust conference with 850+ attendees. We give free tickets to all the speakers and volunteers, which is almost a hundred people total. The sponsor packages also include a total of roughly 100 tickets. That leaves ~650 sold tickets.
Those are roughly 250 corporate tickets (~410 euro after tax), 300 individual tickets (~190 euro after tax), and 100 student tickets (~30 euro after tax). Accounting for the various discounts (early bird, discount codes, etc.) and overhead, this leaves us with roughly 140k.
Those student tickets are sold at a significant loss, but it's very important to us to not just run this conference for those with a well paid job.
Setting the ticket prices is very tricky, because you have to set them a year in advance, before you know what amount of sponsorship to expect. We only find out *after* the event if we guessed correctly or if we ran at a loss. This year, we made a (very small) profit, which we'll spend on our Rust Maintainers Team: https://rustnl.org/maintainers/
Chapter 1 of our new "C to Rust Migration Book", written by @unsafe, is out now.
We distilled our experience modernizing critical software into a self-paced course: FFI fundamentals, safe mixed C-Rust codebases, and of course some best practices we’ve developed.
Read it for free now 👉 https://mainmatter.com/c-to-rust-migration-book/
RE: https://fosstodon.org/@mainmatter/116844683436105215
Check out our new C to Rust Migration Book! @unsafe et al compiled experiences from working with clients on large-scale Rust migrations into a practical guide 📖🦀
Last week, we released the first chapter of our "C to Rust Migration Book", written by @unsafe. Drawing on our experience modernizing critical software, it's a self-paced course covering FFI fundamentals, safe mixed C/Rust codebases, and best practices.
Read it for free 👉 https://mainmatter.com/c-to-rust-migration-book/
Rewriting a C codebase in Rust is hard, and it's easy to get wrong. We’re hosting a free AMA with our @algo_luca and @unsafe, author of the C-to-Rust migration book, to answer your questions on migrating C/C++ to idiomatic Rust.
Register now 👉 https://luma.com/m2gplobz
people IT HAPPENED after _3 years_ k23’s fork of cranelift has finally been deprecated in favor of upstream cranelift!!!
huge shoutout to the team for their continued no_std work!
veeery rough around the edges (you need to disable acpi in utm, backtraces are broken, and shutdown drops you into a panic loop) but its a good start!
most of that boot time is taken up by the (very slow) uefi firmware, k23 takes roughly 60ms to boot. not great either but at least were booting!!