I just thought it would be nice.
My recent incompetence is humbling. I should quit the industry.
Three cheers for dropping things that are too complex.
+Great.
+This is one special case.
+This slippery slope is long and steep. I'd prefer not to take the first step.
+All that aside, the rule works very well in practice.
+dot dot dot
+Sounds nice.
+Yes.
+It is legal.
+At MIT the server is the unit of invention.
+Nothing is wrong here.
+Да!
+Noted.
+нет.
+THIS OPUS LACKS PERSPICACITY
+THIS INCHOATE EMISSION DOES NOT ADUMBRATE CONSUMMATION
+OK I'll stop now.
+Russ is prepping some words about what's happening.
+I will fix.
+Feature requests will be ignored.
+I would call that a bug.
+Feel free to file an issue.
+I really dislike knobs in APIs.
+???
+What's wrong with the obvious?
+I am dyspeptic.
+I do not.
+The Yacc grammar was translated by sam-powered hands.
+Turning off comments.
+This is unfortunate.
+NaN is unfortunate.
+No we can't.
+go away
+You misinterpreted my suggestion.
+Not a great situation, I admit.
+I do not understand your criticism.
+If you want to do the work, I will review the results.
+Now, this is one of the things where the guy who blogged about me being a world-class jackass missed the point.
+Please drop this.
+Maybe yes, maybe no.
+Please be respectful in this forum.
+It sounds reasonable and should be easy enough to implement.
+There is a widespread assumption that garbage collection and kernels cannot coexist but history shows a number of examples that demonstrate otherwise.
+Speaking as a one-time kernel writer, I would have loved to have garbage collection available inside the kernel. Hell, half the code in the kernel is tied to memory management.
+Thanks for the report.
+It takes precautions but there are no guarantees.
+What is the problem you are trying to solve?
+Please be civil.
+I think this would be a mistake.
+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.
projects / plan9front.git / blobdiff