> DRY is a great suggestion but shouldn't be looked at as any type of hard rule Agree that nothing should be a hard and fast rule. But the significance of DRY

> DRY is a great suggestion but shouldn't be looked at as any type of hard rule Agree that nothing should be a hard and fast rule. But the significance of DRY is that it increases quality. Not even having the option to "stay DRY" for many problems implemented in Golang will increase bugs. That's just how it is. Given the tradeoff between the supposed complexity of generics and the very real cost of bugs that will happen from maintaining duplicated code, I'm not sure there's much of a debate to be had.