# An Open Letter To The Go Team About Try

DevFeed: [An Open Letter To The Go Team About Try](<https://devfeed.tech/articles/an-open-letter-to-the-go-team-about-try-22146.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2019/07/an-open-letter-to-the-go-team-about-try.html>)

Published: 2019-07-01T00:00:00Z

Content type: opinion

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [ardan-labs](<https://devfeed.tech/tags/ardan-labs.md>), [blog](<https://devfeed.tech/tags/blog.md>), [developers](<https://devfeed.tech/tags/developers.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [go](<https://devfeed.tech/tags/go.md>), [go-error-handling](<https://devfeed.tech/tags/go-error-handling.md>), [go-programming](<https://devfeed.tech/tags/go-programming.md>), [golang](<https://devfeed.tech/tags/golang.md>), [programming](<https://devfeed.tech/tags/programming.md>)

## AI overview

An open letter argues that the proposed Go try mechanism is not sufficiently supported by available survey and proposal data. It questions whether most Go developers need improved error handling and whether introducing a second error-handling mechanic is the right design.

## Source excerpt

"Once a language gets complex enough, programming in it is more like carving out a subset from an infinite sea of features, most of which we'll never learn. Once a language feels infinite, the costs of adding further features to it are no longer apparent". - [Mark Miller] (https://medium.com/@erights/the-tragedy-of-the-common-lisp-why-large-languages-explode-4e83096239b9) The new try proposal is an addition to the language that introduces a second mechanic to handle errors. It is being introduced in response to data gathered from the 2018 Go Survey and a review of proposals that were submitted during the Go 2 proposal process. The conclusion the Go team made from these data gathering exercises was that Go developers wanted better error handling.