if something works - and works well for its purpose - then where on earth is the point in constantly tweaking / altering / modifying / changing it purely for the sake of it, hm? Unless, of course, said changes are requested by real-world users, in order to make working with it easier for all concerned.
In other words, responding to "constructive criticism" rather than "change for its own sake" purely on a whim.
(
shrug...)
One thing, however, is as true today as it's always been. Change is the only thing in the world that IS constant.....
Mike.
One shouldn't be mislead about change in linux software. Basically, nearly all, or even all software that is maintained, changes regardless of how old the original version of the software was when it was first written and released. Some examples follow.
The major software package of coreutils, which includes the basic commands in linux like
ls,
rm,
mv,
cp etc., one might imagine was pretty much set in the early years of linux. Viewing the changelog however, shows that changes to the code occur quite frequently, a number of which have been as recent as February this year 2026.
In the case of xorg, one might imagine it's been set for many years since it "just works" and has done so for ages. However, it is not an unchanging mass of code. Reading the changelog, for example in /usr/share/doc/xserver-xorg/changelog.gz, it's readily apparent that instabilities have still been identified in recent years and the code gets altered and improved. Maintainers still work upon it to correct or enhance it. It may no longer get new features developed or added, but the latest changes are dated in October of 2025 in my installation of xorg.
Many major linux distros in the early years relied on sysVinit before systemd was developed. Today, there are a number of distros that still run sysVinit or a form of it, not having changed to systemd. Distros that run versions of sysVinit like antiX, devuan and MX, do not run the same sysVinit that was used in the early linux distros. If a user chooses a distro that uses sysVinit, they aren't choosing any identical version of the old traditional system that "just works" and hasn't changed, and therefore doesn't need to be replaced. Rather they are choosing a newly developed and tweaked sysVinit that the distro has prepared and keeps maintained so that the distro keeps working and improving and coping with whatever it needs to as software gets developed around it. Whilst the concept of sysVinit is kept in modern distros that use it, that is, the underlying architecture of runlevels 1 to 6, and the /etc/inittab configuration arrangement, among other things, so much of the surrounding code in the executable scripts has needed to be modernised to cope with modern hardware. SysVinit traditionally executes commands sequentially, but modern developments have introduced mechanisms for it to execute in parallel, which is one of the features of systemd. Modern sysVinit has to be able to work with modern linux kernels and handle things like tmpfs and devtmps filesystems, and has changed to do so. An original version of sysVinit would not cope well with modern demands.
Browsers are another example software with very frequent changes. Today's firefox is quite different to a version just a year ago, let alone any time before that.
All in all, from the above brief considerations, I can't see much validity in the argument users may posit that they don't make a change to a newer software alternative because the old one doesn't need to change. By far nearly all, if not all software that doesn't become abandoned or obsolete, actually changes one way or another to keep up with modern demands, both software and hardware demands.
If a user runs a computer online that has been installed at a point in time without any changes such as further updating or modifying of the software, that computer will shortly become out of date, more vulnerable to failures online such as no longer being to access some sites or function on some sites, more vulnerable to exploits, in danger of being used by illicit hackers and unable to take advantage of enhancements made to later versions of the software on the machine. There are other vulnerabilities and disadvantages too.
Rather than an argument about not wanting to change, I see the preferences users declare for sticking with some particular software as having other valid reasons. One might prefer a modern sysVinit style distro because it's a leaner system, more economical on resources than a fully-featured systemd system. They might prefer an older style browser like palemoon because it's also more economical on resources, or even for aesthetic reasons. They might prefer xorg over a wayland compositor because it runs a particularly preferred window manager or still caters natively for remote GUI connectivity. None of this software however, has been unchanged in its latest versions.
Overall, the argument that one is not changing because they "don't like change just for the sake of change", falls flat in the face of the fact that nearly all software that doesn't become abandoned or obsolete, changes. I think it's disingenuous to try and make the case that developers change for the sake of changing, compared to the notion that they make changes to improve and enhance their software.