←back to thread

Go is still not good

(blog.habets.se)
644 points ustad | 1 comments | 22 Aug 25 09:25 UTC | HN request time: 0.212s | source
Show context
andy_ppp ◴[22 Aug 25 11:54 UTC] No.44983412[source]▶
They are forcing people to write Typescript code like it’s Golang where I am right now (amongst other extremely stupid decisions - only unit test service boundaries, do not pull out logic into pure functions, do not write UI tests, etc.). I really must remember to ask organisations to show me their code before joining them.

(I realise this isn’t who is hiring, but email in bio)

replies(3): >>44983532 #>>44983602 #>>44983720 #
candiddevmike ◴[22 Aug 25 12:28 UTC] No.44983720[source]▶
I do this and think it works really well...

myfunc(arg: string): Value | Err

I really try not to throw anymore with typescript, I do error checking like in Go. When used with a Go backend, it makes context switching really easy...

replies(2): >>44985065 #>>44997272 #
chamomeal ◴[23 Aug 25 16:58 UTC] No.44997272[source]▶
I do actually love returning errors in TS. It solved most of the problems I have with error handling.
replies(1): >>45002752 #
1. andy_ppp ◴[24 Aug 25 09:24 UTC] No.45002752[source]▶
Yes not terrible, I think throwing is often worse. I do think that Golang forcing you to deal with Errors immediately is just a bit extreme, sometimes it’s nice to have a choice or create abstractions about how to handle them.