| > And frankly, yes, Go's approach to handling errors is a Big Deal. It's not. > It's counter to the tendency of the last few years to move more and more error handling into exceptions. Haskell says hi. Go's error handling is a step back not because it tries to avoid exceptions but because it's a crummy very slight improvement over C error handling. Contrary to what you believe, the world has moved on since then, even outside of exceptions-based error handling. > Challenging the exception-handling orthodoxy is absolutely something interesting and new. It absolutely is not new, and there is nothing interesting to the way Go did it (which is a significant downgrade of Erlang's way of handling errors) > Go's type system is absolutely huge in terms of making it special. You have not answered the question. > It would never have attracted the attention it did Of course it would, the attention it attracted is due to its backers, not to its intrinsic qualities (of which it has few, lost in a morass of decisions which would have been bad 30 years ago). |