There’s typically a complex tree of dependencies, where packages all tend to rely on each other in order to function.

I managed to remove it myself this morning...apparently it used to get it's hooks in so deep it was very difficult to remove the daemon as it interconnected with ubuntu-desktop for....reasons.

Dll hell was caused by multiple apps on the same device requiring different versions of dependencies. As dlls were shared that couldn't be resolved. Giving each app it's own versions of its dependencies is a way of avoiding dll hell. I'm not saying this a good thing but it avoids that specific problem.

The worst thing about snap is that it runs contrary to the concept of shared libraries that are easy to upgrade. Each snap package includes the dependencies for the app, which means you may have multiple (vulnerable) versions of a library installed. It's DLL hell all over again from a security perspective.

The upside to snaps is they make installations simpler because they avoid the heartache of dependency hell. This is what occurs when a new application can’t run either because a required resource isn’t available, it’s the wrong version, or its installation overwrites files required by existing applications so they can’t run.

Snap gets rid of dependency mess. Good. Snap offers in one place FOSS and proprietary app’s. Here I am suspicious. It may be an advantage for a commercial app-store and for some users. But this advantage may lead to loss of comfort and flexibility for the many users that rely first on FOSS.