Re:(On | No) Syntactic Support for Error Handling
by 9rx on Wednesday June 04, 2025 @11:27AM
(#44181788)
> but it wasn't a mistake to not have exceptions in Go, it was intentional.
Go has exceptions! It even uses them (see encoding/json, for example). And they are equally there for you to use.
It wasn't a mistake to promote not overusing them, but that sentiment is not unusual. The Ruby community comes to mind as having also promoted favouring error values over exceptions[1] long before Go existed.
Java leaned into a bad idea, but is not exactly representative of the state of the union.
[1] Ruby on Rails went against the grain, while simultaneously marketing itself towards Java developers doing "XML sit-ups", so that sect within the greater Ruby community tends to be more of the Java school of thought.
Go has exceptions! It even uses them (see encoding/json, for example). And they are equally there for you to use.
It wasn't a mistake to promote not overusing them, but that sentiment is not unusual. The Ruby community comes to mind as having also promoted favouring error values over exceptions[1] long before Go existed.
Java leaned into a bad idea, but is not exactly representative of the state of the union.
[1] Ruby on Rails went against the grain, while simultaneously marketing itself towards Java developers doing "XML sit-ups", so that sect within the greater Ruby community tends to be more of the Java school of thought.