My Rust Tech Stack

Conventions

The star(⭐️) indicates that it is a go-to crate for me in it’s problem domain.

Builders

• ⭐️ derive_builder
  • Support lots of features
• bon
  • Allows not just builders for structs, but also for function parameters.
  • However, it’s in its early stages.

Validation and Type Driven Development

• ⭐️ validator
• ️⭐️ nutype: The validator does not support unit structs.

Http Mocking

There are 3 popular solutions for mocking HTTP requests in Rust. Here’s a simple comparison

• ⭐️ wiremock-rs
• mockito
• httpmock

Web Automation

These don’t seem a lot different from each other. However, thirtyfour is newer and seemed to be more feature rich. It seems like the author of thirtyfour has proficiency in web automation, and fantoccini’s author, being John Gjengset, being more proficiency in Rust. (Disclaimer: These are just my intuitive thoughts, without any objective reasoning)

However, since fantoccini has been around for longer, I decided to go with it, and change to thirtyfour if I face any limitations.

• ⭐️ [fantoccini]
• [thirthyfour]

There’s a reddit post of the to library authors discussing the differences, when thirtyfour was released.

Publish

• ⭐️ release-plz: Seems to support more automation
• cargo-release: Doesn’t seem to support GitHub releases.