Go's interfaces were designed to solve particular problems.
Go is not the product of a Whiggish development process.
complexity is multiplicative
+i always intended to fix the problem; i never saw how.
+apologies.
+The choice cannot be explained, only understood.
+Indeed.
+i see no bug here.
+I support the idea of unrecorded talks.
+We do not accept patches
+Syntax highlighting is juvenile.
+Working as designed.
+I've written programs with twenty implementations of io.Reader inside.
+Who cares? Shut up.
+What is wrong with my analysis?
+I just want to explain something.
+I recommend in the strongest terms that you don't do this.
+Sockets are the X windows of IO interfaces.
+Ignore what I wrote.
+In other words, here's how to do it but don't do it.
+I did indeed.
+I don't understand what you mean by 'reset'.
+I am, and as far as I can tell it makes no difference whatsoever.
+Please put this silly objection to rest. It has no merit.
+Interpretations will vary.
+I think the pattern used well is perfectly acceptable in certain situations.
+Like everything that attracts scrutiny, the key point is to use the idea well: safely, clearly, correctly, and only when appropriate.
+I am not trying to be difficult, but you must understand it's not simple to address your question.
+One step at a time.
+Thanks for grinding through those.