Follow
golang things
Reading some Golang code and it sure seems very C-brained in terms of "oh just write your own buffer handling and thread synchronization routines, it'll be fine"
re: golang things (2)
@joepie91 it honestly throws everything we know about building good software out of the window imo.
re: golang things (2)
@bananas I didn't really need to read further than `if err != nil` to get that impression :)
re: golang things (2)
@joepie91 this is "good, actually", it makes all go code "look the same".
re: golang things (2)
@bananas Auditor-me has Opinions about this goal
re: golang things (2)
@joepie91 golang made it quickly to my 'never again' list
golang things (2)
The auditor in me is not very happy about this