Hacker News Reader

Comment by 38 | Hacker News Reader

jesus. both of those examples are awful.

I dont mean that as a statement against the author, I mean it as a statement to the language designers. people are gonna start writing code like this, or worse, and Go is gonna end up like many other unreadable languages. shame.

View on HN

TBH, a lot of the complications in Backward() are because it's dealing with two iterators (one as an input, one as its output) and the input/output are both generics. This isn't a typical case.

Maybe it is just me, but I have a very hard time reading Go in general. I have a hard time with e.g. type annotations without a colon or an arrow. The := operator does not read fluently, and I always have to think about what it does to the variable binding (in python the := reads just fine).

Also, whenever I encounter multiple returns it feels very cluttered and I have to stop and think what the heck is going on.

And finally the the capitalization of variable does horrors to my understanding of the code that I’m reading, I know what it is for, but as I’m reading code, if a function being used is an imported from somewhere else is not a meaningful information, and just confuses me.

I bet there is more, but these are some of the examples I’m consciously aware of

They just sounds like ways it’s different from the language you’re using currently?

I could have written this post, except for exactly everything would be inverted.

It's not just you.

There is something about Go that feels "off" for me as well.

I started picking it up but couldn't get past some of the syntax.

Reply on news.ycombinator.com