3 ms·
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
by throwaway894345 5y ago
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.