> Agreed, it does not necessarily have to be open source. But my opinion is that if the taxpayer's money is used to pay for software, then that software should be open source.
Yes. The government has more than enough leverage to demand this. Skill was never the problem. The problem is bureaucracy; too many regulations and massive hidden corruption. The problem with the regulations is that they were designed with the explicit intent to stifle competition.
"Nobody got fired for choosing IBM" - This fact is pure corruption. I remember, when I was at university, one of the courses I took had a project management component and we did an assessment researching failed software projects and it turns out that there were a huge number of failed projects running in the hundreds of millions and even billions (and that was a lot of money at the time); always the same companies kept coming up. IMO, this is fraud, of a criminal nature. People should go to jail.
> IMO, this is fraud, of a criminal nature. People should go to jail.
I have been in companies getting money from government programs. It's not fraud from the government side, at least not for what I've seen.
The problem is that companies see government programs as a way to make easy money. If the government pays a company for X, that's because that company has expertise in X. So it's easy for the company to bullshit the government employees and sell them crap.
Companies abuse the government funding as much as they possible and legally can, and then we blame the government. And on top of that we would want fewer regulations? If you want to be able to punish abuse from companies, you need regulations, and you need to apply them.
> The problem is bureaucracy; too many regulations and massive hidden corruption
I keep hearing the "too many regulations" argument, and I totally disagree. Too few regulations (or rather no enforcement of them) resulted in the TooBigTech monopolies we have today. Of course, they got so successful because of the lack of regulations, but now it's simply impossible to compete with them. Removing regulations (assuming that there are regulations that impact them today, which I doubt) would help them, not the competition.
And we have precedents:
* Whenever the EU tries to do some antitrust, it impacts TooBigTech (which is almost exclusively US), and as a result the US bullies the EU to stop it. If regulations were weakening the EU, why would the US government fight them?
* Let's continue with the US as the example of fewer bureaucracy in this case (the complaint is that the EU cannot compete with the US because of the EU's bureaucracy): look at examples where a non-US company takes over a market (or threatens to take it over). Huawei smartphones (not the infrastructure like antennas, this is different), TikTok, DJI. What do US companies do to win against them? They lobby like crazy to add regulations that will stop the competition.
The US hasn't managed to compete with TikTok: they made it illegal instead.
When Huawei was becoming very big in smartphones in the US, they got banned.
The US hasn't managed to compete with DJI, and the biggest US drone companies are spending a ton of resources trying to get DJI banned. DJI is so superior that even banning them is tricky: it has to be done slowly because banning them right away would disrupt entire industries for lack of viable alternatives. That's how far US drones are from DJI drones.
"Too many regulations" is wrong. The successful players get protection from their government (be it the US or China), and it's high time the EU protected its own players, too. With regulations, just like the US and China does (when they don't abuse their dominant position to bully the EU).
The big system integrators are often pretty terrible at their jobs but it isn't the only cause.
Extremely expensive software projects in government have a common thread in every case I have first-hand experience with. The government has no consistent vision of what they want or who is the final arbiter of these decisions, and no person in the government is accountable for the outcomes. Both the requirements and responsibility are spread across so many people that for all practical purposes there are no clear requirements and no accountability.
The government software programs that run well in my experience have the organizational equivalent of a BDFL. A BDFL doesn't really exist in government; even when someone acts in that role they are often reassigned to other projects at random.