Fine, all of this being based on an analysis that is statistically meaningless, using a language that doesn't get into the TIOBE top 20, and doesn't mention the (say) off by one errors that are notorious in the world of weakly but statically typed languages like C(++). If you wish to continue with such languages you're more than welcome to do so, I'm sticking with the far safer strong typing of Python as my time is precious to me. I find the tooling for python perfectly adequate for my needs, although I don't understand why these oh so brilliant statically typed languages need tooling, why doesn't the language do it for you?
There is a reason anything safety critical is written in statically typed languages
ADA didn't stop the most expensive single insurance payout in history when Ariane 5 fell out of the sky.
Of course static typing has the major advantage of time saving as you don't have to test your code, once it's compiled you can just go down the pub. The poor buggers using dynamic typing have to stay in the office to test. Unless they're using a strongly typed language like Python, whilst the thickos are using weakly typed languages like C(++). You of course never make this distinction, conflating static and dynamic whilst making no comparison about weak and strong. Hence I'm out of here as there's no point flogging the dead horse that static typing is, it'll never be as cost effective to write as a dynamic language and that's all the great white chiefs think about.
1
u/[deleted] Jan 06 '18
Citations please.