Long term release for Linux #404
-
I took a look at the Linux page: https://www.privacyguides.org/linux-desktop/ prior to setting up a family member with a laptop for them to use, and I found that all of the recommendations require a lot of maintenance. That may be fun for people who are very interested in computing, but for people who want to have something that is an appliance - usable for years and stable, there are no options on this page. Is that something that can be talked about on this page? I know that there seems to be a bias against this kind of stability, but both Apple and Microsoft support this kind of use case, and it would be a pity if this could not be supported on Linux. |
Beta Was this translation helpful? Give feedback.
Replies: 0 comments 16 replies
-
I'm not aware of Microsoft or Apple supporting this type of use-case, could you share an example? LTS distros are generally regarded as being very bad for desktop computing. I would really encourage you to reconsider a rolling release distro for your family member. Sticking them with old, buggy, and outdated code is only going to cause you more maintenance issues, not less. It requires you to make a lot of one-time exceptions and repo additions when it turns out you need something modern, which will in turn leave you with software stacks that interact very poorly with each other. Regular updates are just a click of a button and save a ton of headache in the long-run. |
Beta Was this translation helpful? Give feedback.
-
I would like more details on this one, why would Fedora require more maintenance than Ubuntu/Debian in your opinion? Updates are covered by other responses. |
Beta Was this translation helpful? Give feedback.
I'm not aware of Microsoft or Apple supporting this type of use-case, could you share an example? LTS distros are generally regarded as being very bad for desktop computing.
I would really encourage you to reconsider a rolling release distro for your family member. Sticking them with old, buggy, and outdated code is only going to cause you more maintenance issues, not less. It requires you to make a lot of one-time exceptions and repo additions when it turns out you need something modern, which will in turn leave you with software stacks that interact very poorly with each other. Regular updates are just a click of a button and save a ton of headache in the long-run.