Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
mkcert
A simple zero-config tool to make locally trusted development certificates with any names you'd like.
I'm quite new to Rust, and have been trying to learn more by working on some real solution I could see myself benefitting from, which happens to be a CLI tool at this time. I know there are some great tools written in Rust which I use day to day (such as Starship, bat, exa, etc.), but I wanted to hear experts' suggestions / recommendations on any project I should check out for clean, clear, and extensible structure (or lack thereof), and any dependencies I should start with / avoid.
I'm quite new to Rust, and have been trying to learn more by working on some real solution I could see myself benefitting from, which happens to be a CLI tool at this time. I know there are some great tools written in Rust which I use day to day (such as Starship, bat, exa, etc.), but I wanted to hear experts' suggestions / recommendations on any project I should check out for clean, clear, and extensible structure (or lack thereof), and any dependencies I should start with / avoid.
The main focus of the CLI tool would be around working on filesystem, and also making several network requests simultaneously. Although some may argue it would be easier/faster writing in other languages, this is more for my own learning to write in Rust. It will be a simple toy project at first, but I'd like to prepare for more complex Rust programming in the future with it. For instance, I see different directory / file / module structures used, Rust version / edition differences here and there, some common dependencies such as Tokio, etc.
I'm quite new to Rust, and have been trying to learn more by working on some real solution I could see myself benefitting from, which happens to be a CLI tool at this time. I know there are some great tools written in Rust which I use day to day (such as Starship, bat, exa, etc.), but I wanted to hear experts' suggestions / recommendations on any project I should check out for clean, clear, and extensible structure (or lack thereof), and any dependencies I should start with / avoid.
Flux CLI (for Flux, GitOps) for Cobra based implementation with a clean and extensible setup
Flux CLI (for Flux, GitOps) for Cobra based implementation with a clean and extensible setup
I personally prefer GitHub CLI implementation over Flux's, as the most of the implementation details are handled in separate, "internal" packages, making their responsibilities clear
mkcert for small dependency footprint - a bit more lengthy implementation but the code base is easy enough to follow
kubectl is for sure battle tested, but it involves very Kubernetes specific implementations and is going to be too complicated for the first pointer
Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package
Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package