Onedrive is not a core windows component. It’s not a dependency of other applications. It’s just a Dropbox replacement.
Windows works, and has always worked, just fine without onedrive. Microsoft just doesn’t want you to know that, because they are obsessed with the idea of upselling you on subscription based cloud services.
There’s actually a few different glibc replacements available for Linux.
And if you think OneDrive is essential for Windows then I’d suggest you do a little reading on the history of Microsoft and how they falsely claim dependencies on their own software stacks. Especially the court cases around debundling IE4 with Win98, and DR-DOS vs Windows 95.
Well, "technically" - it wasn't a false claim. It WAS dependent on IE and other things. It didn't have to be dependent - MS made it that way on purpose, so things would stop working without (even though the dependency didn't need to be baked in).
It's akin to adding webview to your application to display a text file, even though you never would display an HTML file. It could have been done another way, but it wasn't.
Except that it was demonstrated that IE could be removed from Windows 98. So Microsoft then claimed that Windows ran slower without IE. A judge (because this whole saga went to court) argued that Microsofts video evidence proving that point was falsified and so Microsoft later also dropped their slowness claim too.
No, it wasn't. There was w98lite and such where you could replace WIndows 98's (i)explore.exe/shell32.dll with a Windows 95 one and yet the rest of the software just ran like nothing, while being able to run IE in a standalone way.
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
