News for hackers. Stuff that matters.

A comment on How generics are implemented in Go 1.18. Parent comment

Re:How generics are implemented in Go 1.18 by kaba0 on Wednesday March 02, 2022 @06:38AM (#30526193)
That’s a bit bold coming from a relatively young language, given that Java has codebases close to 25 years old.

Also, repeating the same code many times due to lack of expressiveness is not the epitome of long-lived software. Essential complexity is non-reducable, the only way we can deal with it is through abstractions.

[ Parent | on HN ]
Re:How generics are implemented in Go 1.18 by throwaway894345 on Wednesday March 02, 2022 @09:20AM (#30527551)
Some of us were around when Java was young and can compare a 5yo Go codebase with a 5yo Java codebase :)

> Also, repeating the same code many times due to lack of expressiveness is not the epitome of long-lived software. Essential complexity is non-reducable, the only way we can deal with it is through abstractions

Repetition is not a big deal in a local context (e.g., error handling or for loops), and Go is rarely repetitive in larger contexts. Gratuitous abstraction is a much greater danger than extra keystrokes IMHO.

[ Parent | on HN ]