Requiring the work done to be made OSS is unfair to the companies which do not want to do that. (But now allowing small companies to bid on the tender isn't an issue)
The government is allowed to set requirements on what they want to receive, and how they want it be be delivered. So technically speaking they can request a can of developers for 10.000 hours, and want to have a fair price in a tender for that. Or you can ask for a software license to allow you to do this and that. Hence if a solution company does not want to deliver such, they will not participate in the tender, but they have been allowed to participate and with a lot of experience might have been able to do so under a reduced cost (much experience in the field, able to reuse previous work). Less money spend is good for the tax payer. But this would still only be able to be used inside the government. Because there is a limitation a public body could act as a private body by the legislation of competition. Imagine the government buying all ground, developing real estate, there couldn't be any competition. The article is about should government require open source software to be independent of suppliers. There are quite a lot of examples where government software development is not about the next "Office" software but in CAD, geospatial, photogrammetry, simulation, urban planning where this software might benefit others. If the government would build a new OS-kernel we would likely all agree this is stupid, what about a competitor to ArcGIS/QGis?
Or you need to set up a system where users can pledge a bounty payment for when the project implements a feature or fixes a bug the user wants.
The problem is not the cost of the new feature development. The problem is the cost of maintaining that specific part in the future (long tail). If the feature is delivered and the bounty is awarded for that, that will not keep in mind the cost by the project maintainer(s). Hence it is likely to attract external bounty hunters, coders for hire, but not what is needed to have a stable revenue for the project itself.
A language that doesn't affect the way you think about programming is not worth knowing.