The meme text itself refers to “frequent” updates. Seems weird to compare apples to oranges, since release updates are not frequent. Even still, updating from buster to bookworm was relatively painless; certainly not 3 hours of reconfiguration. Before that, I was on Ubuntu, and the release updates were also painless; I remember multiple times not needing to do anything except uncomment the sources.list(.d) changes.
[edit: Another quick point. Since Debian/Ubuntu manage configuration for you to some extent, you don’t need to fix configuration files as often as you would need to on Arch, hence not needing to do ~20+ config changes for two years of updates all at once.]
The point of the meme is “Debian users are so proud of not having frequent updates… but when they do update, they have a huge backlog of things to update” … so yes, the fact that it’s not apples to oranges, and yet Debian users act superior is kinda the point.
And I use arch on my desktops but debian on my servers. I understand the difference. and yes, 20+ config changes is a bit of an exaggeration. I more frequently have to do minor tweaks to fix things on arch, but I also don’t need to set aside time to do arch updates “just in case” … because I have had debian upgrades cause weird side effects that wound up taking up my whole day.
The fact that i can go 2 years between those weird update days means I will still use it for my server, because “just security upgrades” is good enough for a server (even though I would love to have an updated tmux and neovim, so i could share config files, but oh well, i can go without config files on my server, debian DOESNT manage user config files, definitely not any more than arch does.). I don’t “not get it” or something. I understand why people use debian, I use it in certain contexts, but it does also have it’s own set of drawbacks.
The meme text itself refers to “frequent” updates. Seems weird to compare apples to oranges, since release updates are not frequent. Even still, updating from buster to bookworm was relatively painless; certainly not 3 hours of reconfiguration. Before that, I was on Ubuntu, and the release updates were also painless; I remember multiple times not needing to do anything except uncomment the sources.list(.d) changes.
[edit: Another quick point. Since Debian/Ubuntu manage configuration for you to some extent, you don’t need to fix configuration files as often as you would need to on Arch, hence not needing to do ~20+ config changes for two years of updates all at once.]
The point of the meme is “Debian users are so proud of not having frequent updates… but when they do update, they have a huge backlog of things to update” … so yes, the fact that it’s not apples to oranges, and yet Debian users act superior is kinda the point.
And I use arch on my desktops but debian on my servers. I understand the difference. and yes, 20+ config changes is a bit of an exaggeration. I more frequently have to do minor tweaks to fix things on arch, but I also don’t need to set aside time to do arch updates “just in case” … because I have had debian upgrades cause weird side effects that wound up taking up my whole day.
The fact that i can go 2 years between those weird update days means I will still use it for my server, because “just security upgrades” is good enough for a server (even though I would love to have an updated tmux and neovim, so i could share config files, but oh well, i can go without config files on my server, debian DOESNT manage user config files, definitely not any more than arch does.). I don’t “not get it” or something. I understand why people use debian, I use it in certain contexts, but it does also have it’s own set of drawbacks.