Our year in Rust

Erik
Co-owner & Director of Open Source
Our year in Rust

Our year in Rust

A company-changing year in a short story,
begins with a thank you, for this new-found glory.

We want to be clear in this prelude,
It is to Rust we owe our gratitude.

Commercial work is what made our company tick,
Now it was the time for an open-source trick.

For funding this work, putting money in our bank,
We have the NLnet Foundation to thank.

Now Statime keeps time; syncs your clock, so precise,
Making the network memory-safe, you know that's wise.

Our timing endeavors were just beginning
Why do one protocol, when with two you're swinging?

This one less precise, more internet-y
We were ecstatic to partner with ISRG

On Rust's versatility we continued to sail.
Spring came, and showed us a sunny trail

At Lightyear, the solar-powered star of Automotive,
we pitched Rust and they went full-on corrosive!

Next, Aerospace? One can only hope...
Putting software in space still felt out of scope.

Thanks to GAMA we can cross that of our list,
Soon a solar sail running Rust will exist!

A summer of love, was our next wish,
Meeting Rustaceans in real life, that is.

We organized meetups, visited London and Berlin,
Connecting with you all was a huge win.

A new connection that is worth special mention,
NLnet Labs, a group with only good intention.

On open-source infrastructure we will work together,
Aiming to make the internet better.

In autumn, we turned our eye to education,
As spreading Rust is in our mission declaration.

More students joining the Rust work-force,
That is the goal of the Rust 101 course.

Ending this year, exciting things are to come,
a collaboration with Ferrous Systems for one.

Our shining example, and friendly mentor,
We are proud to now go together.

The project's name cannot be disclosed at this hour.
A hint? A little tool with great power.

Our next year in Rust will be even more fun,
great people to meet, cool projects to run,

and last but not least, on top of these perks,
the gift of code that - when it compiles - just works.


Epilogue

This was our little story. The things we were able to do thanks to everyone that contributed to Rust. A kind of celebration that we hope you can take joy in.

Thank you, Rust. Thank you, Rust project. Thanks to all who created the language, tools, ecosystem, and community we were able to build on.

Ooh, and thanks to ChatGPT for reminding us of the importance of rhymes.

PS If you didn't make it into this story, it is down to our creative limitations and fear of creating even more horrible rhythms and rhymes.

Erik
Co-owner & Director of Open Source

Stay up-to-date

Stay up-to-date with our work and blog posts?

Related articles

In part 1 of the "SIMD in zlib-rs" series, we've seen that, with a bit of nudging, autovectorization can produce optimal code for some problems.

But that does not always work: with SIMD clever programmers can still beat the compiler. This time we'll look at a problem where the compiler is not currently capable of using the SIMD capabilities of modern CPUs effectively.

Fuzz testing is incredibly useful: it has caught many a bug during the development of NTP packet parsing and gzip/bzip2 (de)compression.

But I've always been unsatisfied with the fuzzer being a black box. When it runs for hours and reports no issues, what do we actually learn from that? In ntpd-rs we've previously had a bug fly under the radar because the fuzzer just did not reach a large chunk of code. So, does my fuzzer actually exercise the code paths that I think it should?

We keep saying that Rust is how we make software safer. In this blog, we'll tackle a real-world vulnerability, 'rewrite it in Rust', and show you the results of our empirical research, both as a high-level overview and a tech deep-dive.