3 ms·

There's a certain amount of work (and therefore money) required to do this. That incremental difference is small for a well designed application, but - someone

There's a certain amount of work (and therefore money) required to do this. That incremental difference is small for a well designed application, but - someone must actually vet and curate the contents of the repo. That tends to slow down execution, leading to scenarios where things like docker a year or two ago from the canonical "trusty" repo were hopelessly behind the "real" docker since docker was evolving so quickly and trusty was by design slowing down. Each commit that went into trusty required a team to submit and a team to approve. That costs money. ;-)

kasabali 9y ago
It is a matter of distribution and release policy and not an inherent limitation of the model. Stable/lts/enterprise distributions have other concerns like preventing regressions and configuration or behavior changes during lifetime of release. Rolling distributions like Arch and OpenSuse Tumbleweed on the other hand can move a lot faster but still provide basic vetting wrt security and sanity of new/updated packages.