Interesting that you make those very small programs in Rust which feels like a huge overhead, but at the same time I feel this would be a way to get into Rust, every time I try something it’s so overwhelming because I’m trying to solve a too big of a problem while learning Rust so I just give up on it.
They surprisingly were. Originally I went with Rust because writing them in bash script would be very inefficient in terms of the number of programs I need to invoke to fulfil the function. Then I ended up learning some systemd basics.
The first chapter of the Rust-CLI book is IMHO a very good place to start for just learning how to build something useful. Of course, it does not replace building a project of your own, but might give you enough of a framework to fit your own ideas into.
I find myself developing random programs that fills my very small niche. Like a program that displays KeepassXC unlock popup on the workspace I am currently on because it doesn’t work as expected when done with window rules. Or a program that displays the status of multiple services in a single table. I feel like I took customisation stuff too far.
Interesting that you make those very small programs in Rust which feels like a huge overhead, but at the same time I feel this would be a way to get into Rust, every time I try something it’s so overwhelming because I’m trying to solve a too big of a problem while learning Rust so I just give up on it.
They surprisingly were. Originally I went with Rust because writing them in bash script would be very inefficient in terms of the number of programs I need to invoke to fulfil the function. Then I ended up learning some systemd basics.
The first chapter of the Rust-CLI book is IMHO a very good place to start for just learning how to build something useful. Of course, it does not replace building a project of your own, but might give you enough of a framework to fit your own ideas into.