4 ms·
I've done my first project with go. Goroutines are undoubtedly cool and I like the strong typing. * Unfortunately error handling sucks (no stacktrace by defaul
by brango 9y ago
I've done my first project with go. Goroutines are undoubtedly cool and I like the strong typing.
* Unfortunately error handling sucks (no stacktrace by default? Let's go back to the days of peppering print statements around just for fun).
* DB support is terrible (I've spent hours doing what I could have done in half an hour with python).
* It's so verbose, even simple things like mapping over an array to create another array requires a for-loop dance. Same for just checking if a value is in an array. Same, obviously for no exceptions which you either love or hate. I hate.
I can't see myself doing any other projects with it.
- zimpenfish 9y agoI get stacktraces from `panic()` - is this not what you're after? goroutine 1 [running]: main.b() /home/rjp/git/godiggy/test.go:8 +0x64 main.a() /home/rjp/git/godiggy/test.go:13 +0x9b main.main() /home/rjp/git/godiggy/test.go:18 +0x9b exit status 2
- brango 9y agoI want to be able to handle errors, pass them up a few functions then log a stacktrace. I don't want to panic everywhere since robustness is important.