Re: Don't shoot the messenger
> As for the ability to fix bugs or add features in FOSS. That is more of a theoretical situation than a real-world one. Almost nobody except the codes developers have the time, resources, tools or ability to make changes. Especially without inadvertently creating a new bug, or altering critical behaviours. Certainly not your "average" user: who thinks Google is the internet and equates that with WiFi.
As for the ability to change spark plugs[1] or add features to a car, this is more of a theoretical situation than a real-world one, certainly for your "average" driver (followed by insult to the driver).
> Almost nobody except the codes developers
Ah, yes, carefully ignoring two[2] things:
1) If you look at OSS projects, you will see that it is not in the least bit unusual to have lots of contributors - certainly far, far more than the person/people who originally developed it and/or have become the ongoing maintenance team. Because, you see, it *is* possible for *competent* programmers to hunt down bugs and add new features - and then run regression tests! Note the word "competent". You can always find a total numpty and point to them as your example, the same as we can find someone who just poured a litre of oil into the hole left behind when they removed the spark plug; and we'll find out soon enough for both of those "fixers" and avoid them in the future.
2) The post you are replying to included the subtle line "Hire any competent programmer to fix it for me". Yes, you can actually hire programmers. Just like you can hire a garage to change the spark plugs. Now, is it as easy, at the moment, to find a decent "software garage"? Probably not. Even for institutions in the EU, like councils, right now they'll probably be idiots and approach Capita.
Oooh, look, there is something that the EU could look at: making it easiert to find and hire competent programmers to fix open source! Nope, I don't claim to have *THE* answer to that right now.
> I have worked for many large companies whose main driver for what software they use is indemnity
Hmm, careful there, indemnity is not the same as getting it fixed. You *may* be indemnified with nothing more than a fix, but that is a corner case.
> not when an amateur developer can be cajoled into looking at the problem.
Again, hire somebody.
A lot of that is attitude - both preparedness and getting away from the ever-encroaching "gotta sue" mindset (refer you back to indemnity). When something breaks on a machine, you either have a service level agreement or you have the phone number of a mechanic. If you are such a large company that you (believe you) can call a "six-figure executive" and you NEED to do that then you have already failed at setting up your own systems (including choosing and keeping on top of your service suppliers). Which takes us down another rabbit hole.
I find the whole "it is all a bunch of amteurs" argument really odd when there is so much noise (which you, yes, you Pete 2, are quite capable of seeing if you read the open source articles, and comments, in Same Fine Organ you are reading today) about "oh, open source is all dominated by contributions from the Big Companies, so little is done by amateurs now". But never mind, just stick with whichever claim fits your beliefs.
[1] yes, I *know* that *you* can change spark plugs, but remember that, just as with coding, most of the people reading this forum are in a privileged position. The "average", most particularly the modal average, person these days would not go near a spark plug. I'd be willing to bet that they don't try to change their car's bulbs either (I've stopped trying to change the bulbs - first because I'm gettng on a bit and my hands are not up to the job but, more importantly, because despite the fact that the vehicles have been getting bigger and bigger the access to the bulbs has been getting trickier and more painful wirh every model)
[2] three, if we count the lack of an apostrophe