Hi Peff, On Thu, 6 Apr 2017, Jeff King wrote:
> And it's not like people on ancient mission-critical systems get cut > off. They can still run the version of Git they were running when their > OS went out of support. You keep baiting me, so I'll bite, after resisting the urge for so long. Let me share a little story of my own. So that this is not some academic, theoretical wanking off, but something very tangible, very concrete, and something very hard to handwave away. As you know, in my previous job I was working as a scientist. Part of my job was to support other scientists e.g. when they were using that really big, really expensive, really advanced and super cool microscope. The "really advanced" part only applied to the hardware, though, they were running a super old CentOS, and everything was clamped down pretty good (as many microscope vendors are wont to do), so there was no way to upgrade the OS (I do not recall whether the drivers were only available for this particular version of CentOS, but it would make sense, wouldn't it, now, as microscope vendors are much more of experts in microscope hardware than in anything vaguely related to software, even if they like to pretend to be experts in both). I did have access to gcc, though. And I did have to get Git working to be able to install and develop additional software on that machine. It did take me a while to get things to compile because of ancient libraries being installed on that machine. Since only trusted people were allowed to use that machine, security on that box was not really an issue. It did make work for my colleagues substantially easier once I could develop on that machine, using Git. Just imagine how thankful I was that support for these old library versions was almost working, still, and the one bigger problem I had was easily solved by a patch that a quick web search found! This. This is the impact of supporting older library versions, even if they are long EOL. Do not get me wrong: I am all for dropping support that is a huge maintenance burden. You probably do not know the full back story, but let me tell you what a relief it was to drop Windows XP support in Git for Windows (and the Cygwin developers can sing several epic, Lord of the Rings sized war songs about that, too). At the same time, I want us to do better than all those maintainers out there who drop backwards-compatibility just for the heck of it, not because it would be a huge maintenance burden. "Everybody should upgrade, anyway" is usually the naive excuse for not knowing why users are often unable to upgrade. Git is incredibly popular, and part of that is due to us being inclusive and open and supporting a wide range of platforms. Yes, we can always do a better job, that is true. We are also doing pretty well, though, and I think that part of the reason is that we weigh carefully the maintenance cost against the benefit of our users. Tiny "cleanup" patches that fail to improve the maintenance burden substantially, and that also make users' lives harder, are rightfully rejected. A little harder work from us maintainers goes a long way to make a lot of users a lot happier. My former self in my former life as a scientist is very thankful for the consideration that goes into each and every "should we drop supporting XYZ?" decision. Very, very thankful. Ciao, Dscho
