Then you are comparing "bank account interest and debt systems" to "embedded drivers".
Or "tax systems" to "embedded drivers".
Or "insurance policy engines" to "embedded drivers", etc.
COBOL is not a use-case, and all of the above could be done in any language. If we are discussing the qualities, ease of training , workforce availability and overall viability of COBOL, it is against the qualities, ease of training, workforce availability and overall viability of other languages.
> We can train up COBOL developers MORE easily than embedded driver devs.
And we can train up web devs more easily than embedded driver devs.
Your argument makes no sense, as it is a false dichotomy. It also entirely misses the point that I stated earlier, that a company does not want to be able to train developers, they already trained developers to be in abundance in the market.
> I've know embedded driver developers and y you're completely wrong
I work in embedded (nowadays audio and display tech), and with driver development (to make said embedded devices useful, previously for high performance datacenter network equipment), and you're completely wrong.
Not to mention delusional regarding COBOL to the point of being a suspect of IBM employment. The only still relevant quality of COBOL is that it does not self combust so we can take our time with replacing it with something contemporary and financially sensible.