Nobody driving across a bridge gives a shit about what tools the people who designed and built it used. But they sure do give a shit about whether it's gonna f

Nobody driving across a bridge gives a shit about what tools the people who designed and built it used. But they sure do give a shit about whether it's gonna fall down when too many big rigs drive across it, or whether a wind at just the right speed is gonna turn it into Galloping Gertie, or any of the other things that professional engineering practice is designed to make sure has been checked for by multiple people along the way from "hey we should put a bridge here" to "here I am doing my boring daily commute and it crosses this bridge". Does your programming language make it harder to fuck up? Is it one that other people can pick up when you've left the project and shit needs changing? Is it one that leaves everyone involved in writing this code more pleasant to deal with than [Shitty Language Goes Here] because they're spending a lot less of the day swearing at the code? That shit, they give a shit about.