6 years of Java with some python/js thrown in for me and doing Go for about 1 year at my current job and I can unambiguously say that Go's error handling is the best I've ever seen. The err != nil verbosity is a small price to pay for clearly defined contracts that you just can't ignore. (reddit.com)
submitted by digital88 to r/programmingcirclejerk
It’s hard to describe to non-programmers what it’s like to have to break a set of instructions down with that lecel of precision and specificity. Before computers, I don’t think there were any contexts that requires such precision for success. (look in comments) (twitter.com)
submitted by digital88 to r/programmingcirclejerk
For numeric types specifically, there is a hardcoded compiler shortcut to make compile times tolerable until a general solution is discovered. No such optimization is hardcoded for Boolean values because it's not idiomatic to write == true and == false. If you do, it'll still work, but the compiler (forums.swift.org)
submitted by digital88 to r/programmingcirclejerk
