Originally posted by GdeR
View Post
Someone running a CNC machining center with a non-networked machine will want to install only once, and just get everything working once. They will only need updates if they find a bug or add new hardware that needs new drivers. In that case, they will want the updates to install cleanly without breaking anything that already works. That's a job for a good, well-supported LTS.
A developer will want the rolling release and may build crucial libraries from still newer versions or even git master, so as to catch breakage caused by library changes before end users get hit with them. For that purpose, any temporary "freezes" in rolling release can be a serious nuisance, invoking bugs in new software written on another distro with a newer version of some offending library, or just requiring locally building and installing the newer version just to rule out the older version as the culprit. Thus the most up to date possible rolling release favors this type of user.
Thus a "fundamentalist" approach to favor rolling over stable or vice-versa is nuts. Different users have fundamentally different needs.
Comment