Anthony Accioly<p>Kotlin and Go couldn't be approaching their error handling pains more differently.</p><p>Go: <a href="https://go.dev/blog/error-syntax" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">go.dev/blog/error-syntax</span><span class="invisible"></span></a><br>Kotlin: <a href="https://medium.com/@internetcreationist/exploring-rich-errors-in-kotlin-a-game-changer-from-kotlinconf-2025-ea11ae23b585" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/@internetcreationis</span><span class="invisible">t/exploring-rich-errors-in-kotlin-a-game-changer-from-kotlinconf-2025-ea11ae23b585</span></a></p><p>TL;DR: While Kotlin is getting rich errors, Go is getting... nothing. And please stop asking for it, the community clearly won't come to a consensus.</p><p>Like it or not, `if err != nil` is here to stay.</p><p><a href="https://accioly.social/tags/GoLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GoLang</span></a> <a href="https://accioly.social/tags/Kotlin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kotlin</span></a> <a href="https://accioly.social/tags/ErrorHandling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ErrorHandling</span></a> <a href="https://accioly.social/tags/LanguageDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LanguageDesign</span></a> <a href="https://accioly.social/tags/ProgrammingLanguages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProgrammingLanguages</span></a> <a href="https://accioly.social/tags/DevThoughts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevThoughts</span></a></p>