3 ms·
The problem with those approaches is that they bundle all the dependencies with the application, rather than using the system libraries. That means that if a s
by MereInterest 5y ago
The problem with those approaches is that they bundle all the dependencies with the application, rather than using the system libraries. That means that if a security bug comes out, I need to (e.g. heartbleed), I need to track down every single application, check their version, cross my fingers that they at least used a shared library and didn't build against the static library, and update each one individually. For well-behaved software that uses the system libraries, I only need to update the system library and be done with it.
I get that snaps are easier for developers because managing versions can be painful. Pushing that pain onto the users isn't the solution.
- xfer 5y agoWindows apps also bundle all dependencies, go check out any dotnet app(all crypto stuff is in some dotnet library..). Windows docs also encourage you to do this. The difference is there is a set of base windows libraries that you can expect, so if you just use those with your win32 program then it's good. But most dotnet apps don't do this. It's just like using Appimage.