Storage is cheap until it isn’t.

On my desktop where I have something like 6 TB of NVME storage because I am a sicko? The only thing that makes me think twice about a flatpak is if I need to give it access to devices or significant parts of my filesystem (yay permissions weirdness).

On my laptop where I can have one drive and replacing it involves opening the entire laptop AND reinstalling Fedora (or dealing with clonezilla/dd)? Yeah… I very much care about just how much bloat I am dealing with. And, as the other person pointed out, flatpaks can balloon REAL fast.

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 appfoo depends in libbar@2:2.9 and so forth. Of course, the reality is that libbar is poorly maintained and has massive API/header breaking changes every point release and was dependent on a bug in libbar@2.1.3.4.5 anyway.

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.

Part of it is that Ubuntu/Canonical so aggressively pushed Snaps which became a huge culture war. So you have people who hate the idea of those style of packages because they hate Snap AND people who hate flatpak because they are Team Ubuntu for some reason.

And the other aspect is that it is incredibly space inefficient (by the very nature of bundling in dependencies) and is prone to “weirdness” when it comes to file system permissions and the like. And many software projects kind of went all in on them because it provides a single(-ish) target to build for rather than having a debian and an arch and a redhad and a…

That’s nice.

That doesn’t work if you are on an airplane (unless you want to spend the entire flight downloading one episode). Or if you just don’t want to deal with hotel wifi. Or if you just don’t want to expose your internal home network at all.

Which is the point and why this is one of those big features of plex that there are so many tickets and requests to get into jellyfin et al. Because yes, you can just copy files from your NAS to your phone’s internal storage (assuming you don’t care about transcoding and the like)… at which point there isn’t much use to a metadata oriented media server/service.

Or you can just set up Plex to always download the next 10 episodes of whatever show you are watching when it has network access. I mean… that probably won’t work (see: 40%) but when it does, it is awesome. Which is the “it just works” functionality.

Which gets back to the issue where, because it is FOSS, it is the greatest thing ever and anyone asking for anything else is wrong and stupid. Which is a shame because if the Jellyfin devs could actually get the “download the next N episodes” functionality to reliably work (even at 80-90%) it would be a killer app. And, for what it is worth, I have liked the devs a lot when I interacted with them in the past. But the users and evangelists are just… what we can see in this thread.

Did they? Or is that still the old hack of “just download the raw file. Your tablet is just a computer”?

Because I didn’t see it advertised on the main web page and a quick google got me to https://github.com/jellyfin/Swiftfin/discussions/364 which is open and abandoned tickets for the ios apps.

https://forum.jellyfin.org/t-offline-downloads?pid=16373#pid16373 suggests it is also in the same boat for android. You can find workarounds but they aren’t using jellyfin.

Which is “fine”. I watched WAY too many movies over the years with VLC on a laptop. But… why are we using a shim to treat a library as a streaming service in that case? Which gets back to Jellyfin just not actually being a Plex alternative for the majority of users.

Yeah.

Jellyfin is spectacular for LAN usage on two computers. Once you start using devices (because, you know, that is what people tend to plug into their TVs…) or going on travel, it rapidly becomes apparent that it just isn’t a competitor.

Hell, a quick google suggests jellyfin STILL doesn’t have caching of media for offline viewing. Plex’s works maybe 40% of the time but… 40% is still higher than 0%.

I have a lifetime pass for Plex and encourage anyone who even kind of cares to get one next time it is on sale (or shortly before the scheduled price hike). I have tried Jellyfin a few times over the years and… it is basically exactly what I hate with FOSS “alternatives”. It isn’t an alternative in the slightest but people insist on talking it up because they want it to be and that just makes people less willing to try genuinely good alternatives.

To put it bluntly, Plex is an “offline netflix” as it were. Jellyfin is a much better version of smbstation and all the other stuff we used to stream porn to our playstations back in the day.