X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=lib%2Frob;h=89cc3315ac522e5243d946e2c25ea8e7e4e3661b;hb=6701679f3a011dc45a96343fc9c703999be72491;hp=c6300b85c582b762450d52b299a014dc18153a7c;hpb=791545f28fd21a4b4c93faab0dafd61656db05c4;p=plan9front.git diff --git a/lib/rob b/lib/rob index c6300b85c..89cc3315a 100644 --- a/lib/rob +++ b/lib/rob @@ -284,3 +284,117 @@ 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. +Hardware has stopped getting faster. Software has not stopped getting slower. +Ah, right. +I disagree. +There is little meaningful difference between bad style and bad practice. +It's come up before. +Ah, nice. the woodpeckers are back. +I recently got the idiotically named but otherwise very well designed, quiet, and comfortable Apple Magic Keyboard. +It sounds like a mistake to me. +What a lovely vacuous platitude. +That is unhelpful. +Reports of the death of Research are greatly exaggerated. +There are already courses being taught in `feminist science' and the trend is sure to continue. +Not quite. +Please file an issue. +I'm not convinced there is a "why" other than "that's what happens". +Working as intended. +Awwww. Sniff. +The operation is not to copy but to snarf. It's called snarf because snarf is what it does. There is no design document. +Automatically deciding what's important in a program's dependencies is not easy. +Thanks +Yes, one could, and that would be a stylistic decision. +Best not to promote the bad idea. +Nil means nothing. +People often spend too much time worrying about the things that don't matter. +Often the reason something was done is more important than what was done. +I believe this is not a Go issue. +Are you running Xcode 8.3? +I don't think so. +Yup. +Code comments can be helpful with unusual situations like this. +The key word is simple. +If I could, I would disallow it altogether. +I completely disagree. +I say leave it alone. +I wasn't speaking metaphorically. +A nil map is like a regular map but it has nothing in it, cannot grow, and takes zero space. +We live in a digital dark age. +Neither of your issues is a problem. +Your ideas may make people happy, which is not a small thing, but do they really help? +What's this? https://plan9.io/ +Consistency is a better explanation. +Code can move. +You might find blog.golang.org/constants helpful. +Over time, everything gets better but also worse and always bigger and more complex. +Nice to see Egreg again. +It wasn't my intention.