indeed, wal-g actually started as a port of wal-e which was Python: https://www.citusdata.com/blog/2017/08/18/introducing-wal-g-...
wal-g was a much larger improvement over wal-e. we're optimizing the margins here
wal-g was a much larger improvement over wal-e. we're optimizing the margins here
https://github.com/wal-g/wal-g/pull/2262
but yes, this is young project, so fair take
The importance of optimizing (resource) margins and having predictable memory usage increases significantly in the DBaaS/Postgres world, where your process coexists and competes with other critical workloads.
Also, WAL-RUS isn’t rocket science. Postgres already exposes a bunch native constructs for WAL archival, making development fairly straightforward even in Rust.
TL;DR: when to choose Rust or Go really depends on the workload and what you are going after.