The thing about boilerplate code, which a lot (most?) of that excess is, is that you can ignore it.
But then there's all this code in your app you're ignoring. The language encourages you to ignore the code that you're working in.
There's another aspect to this: It's not just your code you're ignoring. The odds are you're building upon layer after layer of similarly boilerplate-ridden code. This is fine, until you have to figure out what's actually going on.
In Clojure, if you're calling a function, the odds are good you can figure it right out from that. Every now and again I find that there's one layer beneath the one you want—and these days I find that irritating and excessive, never mind the half-dozen, dozen or more layers you may have to dig down in the object-soup. (Digging soup layers? Mixed metaphor felony!)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The thing about boilerplate code, which a lot (most?) of that excess is, is that you can ignore it.
But then there's all this code in your app you're ignoring. The language encourages you to ignore the code that you're working in.
There's another aspect to this: It's not just your code you're ignoring. The odds are you're building upon layer after layer of similarly boilerplate-ridden code. This is fine, until you have to figure out what's actually going on.
In Clojure, if you're calling a function, the odds are good you can figure it right out from that. Every now and again I find that there's one layer beneath the one you want—and these days I find that irritating and excessive, never mind the half-dozen, dozen or more layers you may have to dig down in the object-soup. (Digging soup layers? Mixed metaphor felony!)