> This hinges on the contracts actually working as intended, which is something they often do not. Code in general rarely does poorly in that regard.

Exactly the same can be said about the legal system. People are just a lot more used to the many existing "glitches" of the legal system in comparison to "bugs" in smart contracts.

The critical difference is that laws can be changed, contracts are immutable.

In fairness, they picked JavaScript as the language to write the transactions in.

People keep losing money making coding mistakes that even "gcc -Wall -Werror" would refuse to compile. Examples: type errors like L1 vs L2 (whatever that even means, not a crypto person), wrong number of function parameters causing some sort of currying, allowing that massive ETH heist a few weeks back.

I'm sure there are hundreds of other similar horror stories.

"-Wextra -pedantic" would protect against even more bugs.

(I'm not saying C is a reasonable choice, just that JavaScript was a laughably bad choice.)

Contracts are mostly written in Solidity. Despite common rhetoric, it doesn't have much in common with Javascript besides curly braces. Solidity is statically typed, has class-based inheritance, and all numbers are integers. Javascript is dynamically typed, has prototype-based inheritance, and all numbers are floats.

Honestly, the language doesn't matter. Most bugs are logic errors or requirements oversights.