There never was an interface problem. The sql libraries opt to accept an `interface{}` instead of `sql.Valuer` as a matter of convenience (so you don't have to

There never was an interface problem. The sql libraries opt to accept an `interface{}` instead of `sql.Valuer` as a matter of convenience (so you don't have to define the requisite methods). It wasn't a technical limitation. > Btw, you don't get a free pass at my other objections just because someone poked a hole in one of them. The other problems still stand. Take them one by one. You didn't mention other problems, you just whined about Go's feature set. You didn't support your opinions with anything debatable, so there's nothing to discuss. > the language designers like to pretend it's not exception handling at all. > You have to name things starting with a capital letter to make them public. Who came up with this convention? It is not shared by any language ever. > There are built-in functions that use generics, but I'm not allowed to write one? Hypocrites.