Ignoring the fact that you're comparing a cloud storage client to what is essentially a kernel wrapper that all software depends on, you actually can remove gli

Ignoring the fact that you're comparing a cloud storage client to what is essentially a kernel wrapper that all software depends on, you actually can remove glibc without breaking things. You just also have to install another libc (say, musl) and replace your software that targets glibc with software that targets musl, or install a glibc -> musl compatibility layer (gcompat). So, yeah. If you actually know enough about libcs to want to get rid of glibc for a real reason, you can do it without breaking things. If you just want to go around and start deleting core system dependencies (which I think is very silly to put a cloud storage client in that bucket, regardless of the brand of cloud storage) without replacing them, then chaos seems to be the goal, and maybe order is the "broken" state for that machine :P