VSHN.timer #218: Should you Rust or should you Go?

Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.

This week, darling, we’ve got to let you know, if you should Rust or you should Go.

1. Let’s start with a clash. Sylvain Kerkour, author of the successful Black Hat Rust book, argues that if you Go, there will be trouble, and if you Rust, it will be double. We know that this indecision is bugging you.

https://kerkour.com/should-i-rust-or-should-i-go

2. The Rust team announced the availability of Rust 1.76.0 earlier this month. This release is relatively minor, with ABI compatibility updates for function pointers, a new mechanism to get descriptive names from type references, and some stabilized APIs. It’s always tease, tease, tease.

https://blog.rust-lang.org/2024/02/08/Rust-1.76.0.html

3. Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter. It’s fast (really fast, thanks to GPU rendering!), open source… and it’s written in Rust. For the moment, only available for macOS, because one day it’s fine, and next it’s black.

https://zed.dev/

4. UV is an extremely fast Python package installer and resolver, and (guess what) it’s written in Rust. Designed as a drop-in replacement for pip and pip-compile, and 10 to 100 times faster! It’s been tested with the top 10,000 PyPI packages, because otherwise, you’ll be here till the end of time.

https://github.com/astral-sh/uv

5. rustic is a backup tool that provides fast, encrypted, deduplicated backups. It reads and writes to standards restic repositories, and can be used as a restic replacement in most cases. And it’s written in Rust! If you don’t want backups, well, we’re not happy when you’re on your knees.

https://rustic.cli.rs/

Do you Rust or do you Go? Exactly whom are we supposed to be? Would you like to share some Rust tips and tricks with our readers, or do you want us off your back? So come on and let us know, and see you next week for another edition of VSHN.timer.

PS: check out our previous VSHN.timer editions about programming: #18, #30, #33, #47, #50, #60, #77, #88, #101, #103, #122, #137, #160, #174, and #198.

PS²: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.

PS³: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.