Always wondered why nobody did more tracing for latency in unneeded/excessive read syscalls. The amount of directories linux binaries search for files is amazing.
Its not just snap, most binaries are excessive in reads, ballpark, 20-30% of legacy paths, missing binaries, symlinks, etc.
Everytime something breaks and you start peeking at whats going on, its a WTF and WHY, and just assume its legacy built on legacy, for some purpose that no longer exists, maybe except in the extremely rare edge cases.
So, here is your daily conspiracy theory: Snap was actually made by Google (and Github/MS) as an effort to tout the performance of Electron apps: "It's twice as fast as snap!"
Its not just snap, most binaries are excessive in reads, ballpark, 20-30% of legacy paths, missing binaries, symlinks, etc.
Everytime something breaks and you start peeking at whats going on, its a WTF and WHY, and just assume its legacy built on legacy, for some purpose that no longer exists, maybe except in the extremely rare edge cases.