This article gave me agita. I'm in a similar boat in that I'm planning to write my own software basically from scratch in Rust, just for the fun of it. But all

This article gave me agita. I'm in a similar boat in that I'm planning to write my own software basically from scratch in Rust, just for the fun of it. But all of the CI stuff and S3 build artifacts and a server running a private cargo repo and a reverse proxy... it gave me serious anxiety. I'm going to stick with a monorepo and Github Actions for as long as I can. I hope cargo workspace support improves for stuff like clippy so I don't hit the RAM problem mentioned here by the time I'll have written enough code for it to be possible. And yeah, Github Actions sucks. But it's cheap and relatively easy. And it's customizable enough for my use case as long as I'm not afraid to write some glue code when I need to... and either make that glue public or let it live inside each repo that needs it. (Please improve everything about Github Actions, Github!)