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

Can't wait to learn how to call C code from your Rust project after reading my previous posts about Rust interop in general and calling Rust from C? Good! If you haven't read those yet, please do, because I'm going to assume you have in this article. We've seen the basics of Rust's FFI, and have experimented with calling Rust from C. Going the other way around, you'll walk into much the same challenges.
The other day I came across Diplomat, an opinionated tool that makes a lot of choices for you. If you've read my previous post in this series, you'll have seen that that can be quite valuable. If you haven't read the previous article yet, do so before continuing to read this one, as it'll help you appreciate the concepts in this post, and it introduces the example as well.

As part of the development of our Precision Time Protocol implementation, Statime, we want to know how it performs compared to other implementations of PTP.

To figure this out, last April we visited VSL, the Dutch National Metrology Institute. There, we performed comparitive precision tests between Statime and Linux PTP.