Like so many conferences this year, RustConf 2020 was a purely virtual event. I’d already helped organize and attended The Perl Conference in the Cloud 2020 as a virtual conference earlier this year, so I knew it could work.
RustConf was very different from The Perl Conference. It was just one day and one track, lasting about five and a half hours with a break in the middle. The conference schedule was incredibly detailed. For example the opening keynote was from 9:35-10:27. And it really was exactly that long. I was totally amazed that the speakers could stick to such strict times until I realized that everything being presented was pre-recorded.
The talk quality was quite high. I believe that the conference organizers worked with each presenter to help them polish their presentation, which is really nice. This may be related to the format, since this wouldn’t be feasible with a much larger set of presentations. And obviously pre-recording helps here since the speakers could do multiple takes (and even do edits if they wanted).
The conference itself was streamed on YouTube, with Discord as a chat server. The organizers set up channels for each talk that were only usable during the talk and were made read-only before and after. This worked quite well. There were also some general channels like #hallway and #jobs and such.
Finally, there was a companion “app”, Meeting Pulse, with the detailed schedule, a place for attendee pictures, and some other features. I say “app” in quotes because it was just a webapp, though it worked fine on a phone. I ran it on my desktop in a second monitor, which was fine, except that it used insane amounts of CPU and GPU and occasionally lagged quite a bit. But this wasn’t a big problem.
I didn’t like every aspect of the scheduling. The first part ran from 11:30-13:00 with no breaks. For anyone organizing an online conference I’d suggest you institute a rule of a minimum of 10 minutes break after 60 minutes of content. This gives people a chance to go to the bathroom and get some food.
There was a two hour “lunch” break, which made sense in Pacific time as it was from 12:00-14:00 but it was from 14:00-16:00 for me, so it wasn’t so useful. I’m all for a mid-content break, but this was really long, and I would’ve just preferred it to be shorter so we could finish earlier. A 30-60 minute break would’ve been better. But neither of these scheduling issues were a big deal, just small things I’d like to see changed if next year’s conference is virtual as well.
And now some brief writeups on each of the presentations …
This wasn’t the first talk but I’m covering it first because it should have been earlier on the schedule. This is a great intro to Rust for those new to the language, covering many language constructs, error handling, writing simple CLI apps, using REST APIs, and more. I highly recommend this if you’re new to Rust and want to learn more. If you’re totally new to Rust and want to get a quick overview of it then watch this talk!
I’m not sure if all the presenters were part of the Core Team, or exactly how Rust is organized. Suffice it to say that all of the presenters are involved in Rust development and/or the community. The keynote mostly talked about Rust as a project and community, and was more on Rust’s values, especially community values. I think it was a good opening since Rust has really positive community values. I hope that made all the attendees feel welcome.
This was my favorite talk overall, with great technical info, excellent slides, and a very polished presenter. Jane talked about the difference between errors, error context, and error reporters, which was really interesting. Rust makes this a bit more explicit than many other languages, especially if you use some of the really nice crates she covered. I highly recommend watching this even if you have no interest in Rust! I’ve been using anyhow and thiserror myself, but she introduced eyre, a fork of anyhow that looks really nice. Plus it’s a funny joke on multiple levels.
This was more of a psychology talk than a technical one, but it was pretty interesting. That said, my way of dealing with my side projects is quite different from theirs. If you struggle with your own side projects, or are just generally interested in psychology, this is worth checking out.
I have less to say about this talk than the others. I just can’t get very excited about scienitific programming topics for some reason, but that’s no dig against the talk or the speaker. The most interesting parts for me was when he talked about using Rust as part of the toolchain for some very big data analysis.
This was a really great talk about how the Rust compiler is designed to teach you how to code in Rust. The compiler’s error messages are one of my favorite things about Rust coding. The only other language I’ve seen that does this as well is Raku, and they got there first. I did plug Raku a bit in chat. I suspect the two communities could get some good error message ideas from each other.
Now we’re talking! I’ve actually considered trying to create a roguelike inspired by Cataclysm: Dark Days Ahead in Rust. I enjoyed learning about Micah’s use of Amethyst. She talked about various aspects of it, including it’s animation system and how that plugs into its overall event loop. If I do decide to work on a roguelike I’ll be checking out Amethyst.
This was more about the hardware and image processing than the science. There were some interesting points about working with low-level interfaces (serial ports), image processing (math I didn’t understand), and using threads to separate controlling hardware from the UI to ensure responsiveness. If you’re a hardware hacker I recommend this talk, but there’s enough general content for anyone interested in Rust.
This was a deep technical dive into how macros in Rust work. The short summary is that they’re extremely powerful. I couldn’t help but think of Raku and it’s goal of making slangs possible. I learned a lot about the Rust macro system, and the talk ended with some programming madness that I think even Damian Conway might envy. I think I learned the most new technical stuff in this talk, with Jane’s as a close second.
I don’t want to say too much about this talk, because that would ruin the fun of it. Suffice it to say that it was both incredibly entertaining and informative, while making a strong case for the benefits of a language that prioritizes safety and correctness along with performance. If you only watch one talk from the conference it should be this one.
Thank you to the RustConf organizers and presenters for your hard work! This was clearly a labor of love, much like the Perl Conference. It’s amazing how much work people will put in for a language and community they believe in.