It is absolutely NOT due to laziness regardless of whether the people are contrators or full-timers.
Where you're making your mistake is in thinking that we're talking about small contractors or individuals. We are not talking about that, we are talking about software / IT houses with employees that have virtually no seniority, they have moderate pay, and they have neither autonomy nor unions, typically. What's more, they're working in a government place where everyone around them has premium pay, premium privileges, premium retirement plans and premium mobility within the biggest employer in Canada. It's demoralising and sometimes, upsetting.
Not every contractor is the one that did Arrive(scam)Can but a lot of them are, too.
Full-timers want to do the right thing because it actually makes their lives easier.
I also call nonsense on this. Full-timers in government are the ones that find a way to do the least amount possible and take the path of least resistance whenever possible. That's why the government has such rotten IT.
It's management penny pinching - thinking regular upgrades are an unnecessary expense (just like they think all IT costs are - to which I tell them we can save millions by turning everything off and oing home).
For the most part, they're right. That's why I related the story about people I know leaving the government (including the DND) when they were forced to switch over to Windows. Because it's been in Microsoft's and their partner's interests to put their customers on a constantly changing upgrade path where forklift upgrades become mandatory - and I mean mandatory, because the IT consultants wrote it into the contracts. This wouldn't happen if we hadn't standardised on the path of least resistance and decided to fund Bill Gates' companies. That bird has flown, however.
They think if something is working fine now, it should continue to work fine forever, then they're surprised when something happens and can't be quickly/easily fixed.
But in many cases, this is true. Not *forever* perhaps, but for long periods of time. I've advocated many times for a dedicated programming staff that standardised on *nix, which is VERY stable from the standpoint of OS capabilities and tools, and perhaps built their applications in the 'web. They would have been 20 years ahead of where they are now and had a BOATLOAD less problems with compatibility, updates, etc. had they done this. But being right doesn't pay the bills of the friends and families contracting for government... good old nepotism is still alive and well.
Kind of like never changing your engine oil because you don't want to spend the time/money to do it because the bike is still running fine.
Not really. There's plenty of software out there that is ancient but still relevant. It all depends on what you pick and who built it. We've been at the stage where most software updates/upgrades are just variations of Teal Blue and re-designed buttons for decades now. A lot of software is very stable and isn't really changing enough to bother upgrading - even accounting software usually only needs tax table changes and otherwise remains the same.