Current workarounds in AppImageĪs an AppImage-specific workaround for the inflexible, static way of how applications are integrated with the system, we have (at least) 4 different, inclomplete ways to integrate AppImages with the system (which still suffer from the shortcomings of the status quo described above but try to work around them): Similarly, when a HTML file is about to be opened, then there is no clear concept which version of Firefox will get to open it under the current XDG regime. macOS does a much better job because icons are stored inside each application, rather than at one central place in the filesystem. The current XDG standard is entirely ignorant of this, assuming all Firefox instances on the system are sharing the same Firefox icon. Firefox, for example, has constantly been evolving their icon. Many applications have different icons for different versions of the same application. Deficiency with the status quo: Multiple versions of applications The same has not happened on "Desktop Linux" for applictions yet, but needs to happen. Once people had mobile devices and roamed around, NetworkManager was introduced and made network management dynamic, assuming that network connections would come and go. This reminds one of the state of networking before WLAN, where everything was configured statically under the assumption that there is a static networking setup that is erected when the machine is installed. Once the external partition containing applications is unmounted, one has to figure out which of the files that were previously copied around need to be deleted, and has to manually trigger various update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |