4 ms·
This strategy doesn't take into account external programs, which may not be compiled/packaged for newly released Ubuntu versions. If one uses many programs fro
by pizza234 5y ago
This strategy doesn't take into account external programs, which may not be compiled/packaged for newly released Ubuntu versions.
If one uses many programs from external sources, and doesn't intend to compile them, it may take some time (ie. at least a few months) to have all of them running on the new O/S.
- sp332 5y agoThis seems backward to me. It's more likely that a new OS version will still have backward-compatible packages, and an old OS version will not support newer versions of apps.
- moffkalast 5y agoWell it's both really, the most sensible version to use right now is 20.04. Not too far back for people to be dropping support, not too bleeding edge to have missing packages. 16.04 is really getting the axe right now.
- pizza234 5y agoIt's both backward and forward :) A lot of programs are dynamically linked; an older O/S may not support some newer librariers, and a newer O/S may not support older ones. While static linking solves this, a hypothetical distribution that is fully statically linked, would take a huge amount space (and memory) - definitely one order of magnitude more (potentially more - a statically linked hello world in go is something like two orders of magnitude larged than the dynamically linked one, although this is an edge case).