like having your IDE cover the other 100 some-odd places of boiler plate such as writing getters and setters, and implementing comparable and hashCode and every other piece of insanity? Also, I much prefer to handle my errors where they happen in the code rather than do Pokemon try/catching. Sorry, the if err != nil horse has been beaten to death already.
> like having your IDE cover the other 100 some-odd places of boiler plate such as writing getters and setters, and implementing comparable and hashCode and every other piece of insanity?
What is insane is believing returning errors is actually handling them, it is not, you're just passing the burden on the caller.
Second, Go isn't free of all the bullhshit you described so I'm not sure what is your point, that you don't have to write getters and setters in Go? lol, off course you do have to.
> Also, I much prefer to handle my errors where they happen in the code rather than do Pokemon try/catching
Who cares, go back playing Pokemon since apparently that's the only thing you can think off and stop being an hypocrite. What do you think panics are? yes, it's an half-baked exception system, like everything in Go, a language designed by people who clearly didn't know what they are doing, for people who don't.
> Sorry, the if err != nil horse has been beaten to death already
Yes, and don't worry, people will keep on beating that horse, because it was designed by people that clearly don't know what they are doing.
