[14:35] CHC tonight if anyone is interested and around [15:41] https://developers.redhat.com/blog/2020/08/12/introducing-the-red-hat-flatpak-runtime-for-desktop-containers/ [15:42] We're recreating Mac applications, poorly [15:43] i dunno, i think it is well. [15:43] What comes to mind for me is "how does this integrate with the DE" [15:43] but probably some room for improvement. [15:43] eg: themes, hints, etc. [15:44] ah yup... "oh, sandboxed, it can't read your theme settings in your homedir" [15:44] "but it can talk to dbus no probably" [15:44] I'm guessing, I have no idea. [15:44] Yeah, DBus is probably handling this [15:44] as soon as I posted that's what came to mind [15:45] Interesting times ahead [15:45] also will be fun if there's a security problem in the container and not all of them get updated [15:45] I never thought that the desktop of the future would be a rack of virtualized machines [15:45] yet, here we are [15:49] not really any difference than a security update in a non-container. [15:50] right, but the chances of an OS update making the fix are higher than the container making the fix [15:53] how so? [15:53] there is nothing that says flatpack gets updated separately from an RPM or DEB. [15:53] notice there is no flatpack separate store mentioned in the article. [15:54] this isn't that snappy b.s. ;) [15:55] Ah [15:55] "A runtime is a filesystem image with system-level libraries and other files. As shown in Figure 1, a system can contain a variety of runtimes, with each being used by multiple applications." [15:56] "In addition to saving space, another big advantage of the runtime separation is handling security updates. If there is a security bug in a system library, we only need to update the runtime, and don’t need to rebuild every application. A runtime can’t possibly include every library that any application would want to use, so libraries can also be bundled with the application. An [15:56] application typically uses a mix of libraries from the runtime and bundled libraries."