after recently reviewing a bunch of go I have concluded that I don't like go
I don't even have a concrete reason for it that I could explain. I even sorta like a few things, such as the multiple returns being a first class feature, although the syntax for it feels gross to me for some inexplicable reason. the language just rubs me the wrong way.
@gsuberland that’s been my conclusion whenever I touch it as well. It’s Fine, but I find it quite tedious to write, and too verbose to read.
@gsuberland I'm starting to feel like I'll never learn a new programming language to the level I know the ones I learned when I was 16-18 (C, PHP, JavaScript...)
I want to love Rust so much but it's so damn difficult.
@gsuberland i have read and worked on quite a few different larger go codebases now and have found the common thread is they are all poorly factored balls of sludge where changing anything involves a whole lot of shit work, and my opinion is that the language just encourages stuff to be built like that
@gsuberland i think go is a prime example of the difference between "simple" and "dumb"
@0xC01DC0FFEE @gsuberland Amos is where I have my second-hand opinions of Go from.
@c0dec0dec0de @0xC01DC0FFEE funnily enough one of the people Amos quotes in that article (expressing an issue with one of the API designs) is a friend of mine. was taken by surprise to see his name in there!
@gsuberland @c0dec0dec0de world is small sometimes :D
@gsuberland my feelings on it are an average of "this language was designed by someone whose head is still in the 80s" and "this language has an undercurrent of contempt for its user"
i don't like it but i begrudgingly admit that it's harm reduction when the alternative is more c
@gsuberland ngl same
@gsuberland and by undercurrent of contempt i mean rob pike _did_ say it out loud
@whitequark wow the fuckin ego right there