All Jellyfin has to do is not mess with users; they'd constantly gain converts as Plex Inc. continues to squeeze its userbase for more money after a decade of unsustainable lifetime plex pass...
All Jellyfin has to do is not mess with users; they'd constantly gain converts as Plex Inc. continues to squeeze its userbase for more money after a decade of unsustainable lifetime plex pass sales.
What were the project heads thinking to rebase to such an idiosyncratic and wide-reaching fork. Wouldn't this majorly inhibit their ability to work on the codebase since there have been so many large changes without any community/devloper input?
I was very confused with the 3.0.0 version, indeed, but since I don't follow its development, have no idea the reasoning they had to release such a disruptive update. Anyway, I agree with you,...
I was very confused with the 3.0.0 version, indeed, but since I don't follow its development, have no idea the reasoning they had to release such a disruptive update. Anyway, I agree with you, specially with software that's more “appliance”/utility than service, such as an on-demand TV app. The less it changes the better. I can see myself sticking to the Legacy app for the foreseeable future — it's that better than the new one.
The outcome that took me to write this down pleases me, even thou it may not appear on the article: keeping Jellyfin for Roku OS old app (“Legacy”) around, alongside by the newer one. Not sure if...
The outcome that took me to write this down pleases me, even thou it may not appear on the article: keeping Jellyfin for Roku OS old app (“Legacy”) around, alongside by the newer one. Not sure if maintaining two apps is sustainable in the long term; meanwhile, I'm glad I'm able to keep using my preferred version.
Is this weird update specific to just the Roku version of jellyfin? I mostly watch jellyfin through the android TV version of the app and don't want to be jump scared by horrible ui when I get home.
Is this weird update specific to just the Roku version of jellyfin? I mostly watch jellyfin through the android TV version of the app and don't want to be jump scared by horrible ui when I get home.
All Jellyfin has to do is not mess with users; they'd constantly gain converts as Plex Inc. continues to squeeze its userbase for more money after a decade of unsustainable lifetime plex pass sales.
What were the project heads thinking to rebase to such an idiosyncratic and wide-reaching fork. Wouldn't this majorly inhibit their ability to work on the codebase since there have been so many large changes without any community/devloper input?
I was very confused with the 3.0.0 version, indeed, but since I don't follow its development, have no idea the reasoning they had to release such a disruptive update. Anyway, I agree with you, specially with software that's more “appliance”/utility than service, such as an on-demand TV app. The less it changes the better. I can see myself sticking to the Legacy app for the foreseeable future — it's that better than the new one.
The outcome that took me to write this down pleases me, even thou it may not appear on the article: keeping Jellyfin for Roku OS old app (“Legacy”) around, alongside by the newer one. Not sure if maintaining two apps is sustainable in the long term; meanwhile, I'm glad I'm able to keep using my preferred version.
Is this weird update specific to just the Roku version of jellyfin? I mostly watch jellyfin through the android TV version of the app and don't want to be jump scared by horrible ui when I get home.
AFAIK, it's only for the Roku version.