3 ms·
>Exceptions are ugly Indeed, you can end up with an indeterminate state. Tell you one thing: writing the if err != nil boilerplate in Go is isomorphic to writ
by blablabla123 14y ago
>Exceptions are ugly
Indeed, you can end up with an indeterminate state. Tell you one thing: writing the if err != nil boilerplate in Go is isomorphic to writing try { ... } catch { ... } for each function call in a way that your state stays clear. The difference of the former is, it reminds you all the time to do this.
- happy_dino 14y ago> Indeed, you can end up with an indeterminate state. No. I think that claim is hysterically funny considering that Go developers almost never check all FOUR states of Go's style of error handling. The problem Go is solving here wouldn't even exist if they had designed/used a better language in the first place. Maybe Go people should stop drinking so much Kool-aid, because they sound like all these Node.js-ninja-rock-star kids who think that they revolutionize asynchronous programming while they reinvent threads, badly.