4 ms·
[Go] doesn't show much awareness of advances that have already been made. Go's response would be to question that the things you're talking about are, in f
by redbad 14y ago
[Go] doesn't show much awareness of advances that have
already been made.
Go's response would be to question that the things you're talking about are, in fact, unqualified advances. Especially in the context of large (ie. LOC) systems applications, maintained by large (ie. dozens to hundreds) of developers.
- Locke1689 14y agoJava, C#, Python, Lisp, and Erlang would all criticize Go for an unqualified new exception system which has not proven that it can handle itself in the context of large systems applications, unlike all the previous languages.
- redbad 14y agoJava, C#, Python, Lisp, and Erlang would all criticize Go for an unqualified new exception system panic/recover is not an exception system in the sense that you mean. Nobody is writing large applications and using panic/recover for error handling. (At least, I hope not!) The idiomatic way of handling errors in Go is returning them explicitly, and checking for them at the call site. func canFail() (int, error) { ... } value, err := canFail() if err != nil { // handle }