▲ | akimbostrawman 3 days ago | ||||||||||||||||
>single shot application instances using 95% of system resources each power cycle Source? There is no measurable energy or efficiency difference at least for flatpak on any semi recent hardware. I know that snaps do take couple seconds longer at first start. I prefer flatpaks for proprietary and internet facing applications because of there easy sandboxing capabilities. There is also the advantage on archlinux not needing to do a full system update for a single application. | |||||||||||||||||
▲ | Joel_Mckay 3 days ago | parent [-] | ||||||||||||||||
People often started here: https://tldp.org/HOWTO/Program-Library-HOWTO/shared-librarie... Getting into why the community argued for years while Debian brought up deb version controlled packaging is a long dramatic conversation. Some people liked their tar ball mystery binaries, and the .so library trend started more as a contest to see how much people could squeeze out of a resource constrained machine. In a single unique application running context, the power of a cached .so reference count are less relevant. As a program built with .so may re-use many resources other programs or itself likely already loaded. > ldd --verbose /usr/bin/bash > ldd --verbose /usr/bin/cat Containerization or sand-boxing is practically meaningless when punching holes for GPU, Network, media and HMI devices. Best of luck =3 | |||||||||||||||||
|