|
|
|
|
|
|
by sophacles
42 days ago
|
|
|
When I was working on large python code bases, a full 50% of my time was spent dealing with tests failing because: * someone assumed duck typing where it wasn't or the inverse. Or changed the assumed interface of a duck. * somewhere doesn't handle None properly even though it's a valid agrument. * making sure every function properly checked that the input parameters were valid and generated a meaningful error message * making sure side effects of the ducks and the meta-bs didn't break other things AKA all type related nonsense. With go, and even more-so rust, the time the compiler saves me by obviating all that type related testing is far larger than the time spend dealing with the type related testing. Even when you factor in the extra time twiddling with types adds to the coding. And don't get me started with the whole "deal with type bullshit in dynamic languages" mess that occurs when a bug slips through into prod.... |
|
|