We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.
A lot of flatpaks early on wouldn’t survive a major point release upgrade or worst case would hold on to dependencies and the user would end up with an unbootable mess after an upgrade.
I haven’t seen that recently though.
However I regularly run appimages on my fedora silverblue system so take what I say with a grain of salt.
If dependencies are articulated (and maintained…) properly, it is very doable and is intrinsically tied to what semantic versioning is actually supposed to represent. So
appfoodepends inlibbar@2:2.9and so forth. Of course, the reality is thatlibbaris poorly maintained and has massive API/header breaking changes every point release and was dependent on a bug inlibbar@2.1.3.4.5anyway.Its one of the reasons why I like approaches like Portage or Spack that are specifically about breaking an application’s dependencies down and concretizing. Albeit, they also have the problem where they overconcretize and you have just as much, if not more, bloat. But it theoretically provides the best of both worlds… at the cost of making a single library take 50 minutes to install because you are compiling everything for the umpteenth time.
And yeah… I run way too many appimages too.