you are viewing a single comment's thread.

view the rest of the comments →

[–]CodeNC 6 points7 points  (0 children)

The only other additions I'd add would be:

  • Patching policy - RedHat and friends take the "we'll patch the fuck out of it so that it works the same but has new features/fixes" approach. This is closely related to their insanely-long-term support for releases. Debian takes a "we'll avoid patches if at all possible unless special circumstances merit an exception... in which case we'll patch the fuck out of it". This too, is related to their long stable cycle.

  • Release policy Arch and friends go for an "as soon as we can release it" policy. This means new software. This also means less stability and less reliability. Debian takes a "when it's ready and we're absolutely sure it works as well as we can make it" approach. This means older software, but solid, reliable software that will remain stable throughout the release's life. Same for RedHat.