@gloopsies @bufalo1973 it's also very much an admission that shared libraries and shared dependencies failed to do what they set out to accomplish, and an admission of defeat. "yes, multiple copies of things that do almost the same thing will have to exist on disk, and in memory space, only because they're all slightly different" and it's maddening.
@gloopsies @bufalo1973 i have a Microsoft sysadmin friend (yes, the "come to the dark side" Darth Vader jokes have already been cracked) and i wanted him to understand the situation with Snap. we chat in Norwegian. here's a translation of how i explained it to him:
"it's a bit like how you, on Windows, need umpteen different versions of Microsoft's Visual C++ library to make all your software work."
"and in recent years, the .NET Runtime. not to mention DirectX versions."
"one has, in the Linux world, tried quite hard to not end up in that situation."
"the Snap/Flatpak stuff lean more toward, no, it's not possible that all the programs use the same versions of various libraries and can live in the same environment, so they need to be isolated more. understandably, this results in a simple chat program eating 1 GB of disk space and 4 GB of memory because each program insists on running its own version of the Chrome engine. and that a chip that, on paper, should bring a space ship to the Andromeda galaxy, in practice uses all its energy on displaying a user interface that the user mainly employs to look at cats on Facebook."
@gloopsies @bufalo1973 i have a Microsoft sysadmin friend (yes, the "come to the dark side" Darth Vader jokes have already been cracked) and i wanted him to understand the situation with Snap. we chat in Norwegian. here's a translation of how i explained it to him:
"it's a bit like how you, on Windows, need umpteen different versions of Microsoft's Visual C++ library to make all your software work."