Often when we talk about verbosity in a language, we mean something is needlessly descriptive in a way that can make things tedious or hard to maintain. Just y

Often when we talk about verbosity in a language, we mean something is needlessly descriptive in a way that can make things tedious or hard to maintain. Just yesterday I made the joke that you can recognise a Java developer at a party because they start almost every sentence with "public static void". Ha. See, funny? Go's verbosity feels different, and I don't think it's "verbose". It's clear. It's about making it really clear what is happening. What surprises me about the proposal is that they think that go's error handling does not reduce the number of errors, because in my experience it does in fact reduce the incidence of run-time errors significantly, and also makes it very clear how to maintain error handling code. I'm not sure I like the try proposal, but I'm not sure I hate it. What I do know is that the verbosity you're complaining about doesn't feel to me like the same kind of verbosity I complain about in other languages, somehow.