Comment by garblegarble
2 years ago
>This may be less pain overall (much like making many small pull requests vs one giant rewrite).
Just shows how different people are in their approaches to dependencies... I can't imagine working like that, the idea that everything I'm using could break at any moment. I'd rather deal with those (possibly larger in number at one time) set of changes at fixed upgrade intervals, in exchange for having a stable system.
A stream of small changes is easier to migrate automatically, so you rarely see a need to update something by hand.
But when you do, the change is small, so you do your adaptation in 5-10 minutes, and continue with your day.
This is in stark contrast with upgrading from an LTS version, when the changes are sometimes drastic, and the changes are everywhere, so it takes some time to even figure out where to start. Because of that, such upgrades may be postponed, snowballing out of hand. I have a box that still runs old-old-oldstable Debian because of that.
A rolling release avoids this, while also bringing you fresh software faster. I get new releases of Gimp or Emacs within a week, and of Firefox, or stuff like git, usually next day.
I have a system that is rolling doesnt mean i work on rolling, that’s why virtualisation exist, i develop in containers that represent preference of clients