Conversation

I fail to see why anyone would use #golang. Yes, it is performant but it has no generics (yet), no error handling (err != nil x 20000), no functional utils like map, filter (yay verbose for loops). No ternary, no string interpolation. It does not even have a Set data structure.

Replying to

Hahaha, I wondered this for a long time, until I found myself reading way more golang than writing it. The lack of magic makes it a very easy language to read/review/maintain

Replying to

and

+1 to lack of magic... until one runs into heavily reflected Go code.

Replying to

and

Agreed on the heavily reflected Go code. There's a bit of Go I wrote a year or so ago to manipulate JSON that I still don't fully understand. But apart from that — +1, total readability + maintainability.

5:24 AM · Jun 8, 2021Twitter Web App

Replying to

and

I guess I haven't used Go long enough to see it's maintainability. But I think it can go both ways. Extreme magic could be bad but not having simple building blocks like map, filter, sets, ternary operator etc just makes writing everything verbose and very repetitive imo.

Replying to

I feel like generics will solve quite a lot soon enough. Very often I've found myself wanting to abstract away a generalisable functionality and Go gives me no choice but to repeat myself. And reflection just obliterates performance.