3 ms·
An opinion (not my blog) about Flatpak (just to trigger discussions): https://ludocode.com/blog/flatpak-is-not-the-future https://ludocode.com/blog/flatpak-is-n
by palata 3y ago
An opinion (not my blog) about Flatpak (just to trigger discussions): https://ludocode.com/blog/flatpak-is-not-the-future https://ludocode.com/blog/flatpak-is-not-the-future
- sph 3y agoOne day we will be able to talk about Flatpak without being sidetracked into deconstructing this stupid post. (And the one at flatkill.org — I've seen it posted so many times it's burned in my brain) Alas, today is not that day.
- palata 3y agoSorry, I'll shut up.
- peter_d_sherman 3y agoInteresting article! My takeaways: >"The current solutions involve packaging entire alternate runtimes in containerized environments. Flatpak, Snap, AppImage, Docker, and Steam: these all provide an app packaging mechanism that replaces most or all of the system’s runtime libraries, and they now all use containerization to accomplish this." [...] >"All of these technologies are essentially building an entire OS on top of another OS just to avoid the challenges of backwards compatibility." This is basically using containers to replace all system libraries -- to insure that a downloaded binary app always works. From this point forward, we'll use the term "API" to represent not just Linux kernel syscalls, but the totality of all library calls (system and otherwise!) used by a given downloaded binary application! Observation: API (in-)consistency (AKA "Stability") one Linux version to another, one Linux distro to another -- is the real problem! That's the real cause! Because everything else, everything else, is effect, not cause! The containerization, the bloated "everything but the kitchen sink" downloads, are the effect of the problem of API (in-)consistency! Phrased a simpler way -- there is absolutely NO guarantee of consistency between the libraries, system and otherwise, of any two Linux distros! So if a binary app is to run on all Linux distros -- then it had better damn well better make sure that the exact specific version of all of the libraries that it needs -- are managed by it, not the host operating system! Containers and bloated library downloads -- are (unfortunately) currently necessary to provide this! Related: "Linux Library Mismatch": https://www.google.com/search?q=linux+library+mismatch https://www.google.com/search?q=linux+library+mismatch "DLL Hell" (the MS-Windows equivalent) https://en.wikipedia.org/wiki/DLL_Hell https://en.wikipedia.org/wiki/DLL_Hell Software Engineering: Bertrand Meyer, "Design By Contract": https://en.wikipedia.org/wiki/Design_by_contract https://en.wikipedia.org/wiki/Design_by_contract API Contracts: "What is an API Contract?": https://www.youtube.com/watch?v=-qM__ozdHCU https://www.youtube.com/watch?v=-qM__ozdHCU Eelcho Dolstra: "The Purely Functional Software Deployment Model": https://edolstra.github.io/pubs/phd-thesis.pdf#page=11 https://edolstra.github.io/pubs/phd-thesis.pdf#page=11 Image-based Linux distributions and associated tools: https://github.com/castrojo/awesome-immutable https://github.com/castrojo/awesome-immutable Spencer Baugh: "Managing Dependencies": https://catern.com/posts/deps.html https://catern.com/posts/deps.html