> Stay away from Manjaro and Pop as they have a history of breaking packages Further to that, if you intend to use valgrind as part of your development workflo

> Stay away from Manjaro and Pop as they have a history of breaking packages Further to that, if you intend to use valgrind as part of your development workflow, note that valgrind sometimes stops working on Manjaro and languishes that way for months. For complicated but ultimately boring reasons that you can research for yourself, the issue isn't resolved by reverting to a previously working valgrind package. I was on the verge of switching from Manjaro to Arch for that reason but lately it started working again so I'm giving it a reprieve. If I were starting fresh I'd use Arch.