7 ms·
Since you didn't add anything other than an unwarranted attack on the person you're replying to, this falls under “Avoid gratuitous negativity”: https://news.y
by acdha 9y ago
Since you didn't add anything other than an unwarranted attack on the person you're replying to, this falls under “Avoid gratuitous negativity”:
https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- fredmorcos 9y agoAlright, let's recap the situation here: Someone spurs a random, obviously incorrect and unfounded piece of information just to make a point about how they use/used huge amounts of data, because big data these days. Then they make it clear that it's just a memory, a less than vivid one: > I agree, all I remember is that when I tried it, /dev/zero sometimes sucked performance-wise Only sometimes yes. Sometimes it didn't suck. But sometimes it did. But sometimes it didn't. > I can't recall the exact circumstances as it was some time ago A long time ago /dev/zero sometimes suck performance-wise, and sometimes it didn't. But sometimes it did. > and could have been on any of Linux/FreeBSD/SunOS/HP-UX/IRIX Ah yes, _could_ have been on any <RANGE FROM THE MOST COMMON UNIX SYSTEM TO THE LEAST COMMON SYSTEM THESE DAYS SO THAT WE INTRODUCE SOME MORE CONFUSION AND ILLUSION INTO THE ARGUMENT>. > perhaps it was the fastest common way at the time? Ah yes, perhaps. Another layer of indirection in the argument. And now the number of possibilities is endless, if you want to find any real evidence of the argument made there, you have to go through hoops and combinations of combinations and run the tests. But wait... > On a recent x64 Linux, /dev/zero seems plenty fast enough now: Ah yes, of course, make sure you're not wrong when it only comes to something others can _easily_ call you out on. Seriously, is HN fostering a culture where it's OK to spew pseudo-intellectual garbage as long as you're being nice? This contradicts how every comment is trying to look like a paper published in a highly acclaimed journal.
- joosters 9y agoOh dear. So sorry that my memory is crap enough to not provide you with the exact details you require. ...every comment is trying to look like a paper published in a highly acclaimed journal It was an anecdote about my previous experience with 'yes' and /dev/zero, it seemed somewhat on-topic. I'm not trying to justify anything or win magic internet points. If you're expecting journal-quality posts, perhaps you should go read a journal and not an internet forum chat.
- fredmorcos 9y agoWhat you write doesn't bother me. What bothers me is that it's not OK for me to tell you that what you wrote is garbage.
- pyre 9y agoYou're free to spout your vitriol just like the people downvoting you into oblivion are free to use their downvote ability to express their dislike with your attitude. Free speech means you're free to express your ideas, it does not mean everyone else is forced to listen to them. It's hard for me to view your comment as anything other than flamebait. You're calling out someone in an aggressive tone, "You don't even know what you're talking about! Bah-humbug!" and then crying crocodile tears that other people are "being mean" to you.
- fredmorcos 9y ago> You're free to spout your vitriol just like the people downvoting you into oblivion are free to use their downvote ability to express their dislike with your attitude. Free speech means you're free to express your ideas, it does not mean everyone else is forced to listen to them. Did I disagree with that anywhere? Do you have a reference comment by me to point to? > It's hard for me to view your comment as anything other than flamebait. Ok. > You're calling out someone in an aggressive tone, "You don't even know what you're talking about! Bah-humbug!" I said I don't think they know what they're talking about. Without any of the shenanigans you portray here. > and then crying crocodile tears that other people are "being mean" to you. What? Where did I claim anyone is being mean to me? I made my argument to everyone who asked why I was being combative. So again, do you have a reference comment by me to point to?
- sanderjd 9y agoThis is a great example of not reading charitably. You're reading a bunch of stuff that just isn't in the text you're replying to. Who said anything about big data? Who is trying to write journal publication quality comments? You seem to have an axe to grind that has nothing to do with this thread. My reading was just that the parent commenter was telling a story by relating an interesting anecdote. That's exactly what I come here for. People won't do that as much if the common response is weird aggression like your comments in this thread. That would be a shame. You could have just written a little comment saying, "in my experience, you're incorrect about the speed of reading from /dev/zero". The difference in your remembered experiences and your conversation about it would have been interesting to me. Instead you picked a fight, which is not interesting.
- fredmorcos 9y ago> in my experience, you're incorrect about the speed of reading from /dev/zero > Instead you picked a fight So I harshly pointed out that they're mistaken. Then it was pointed out to me that I wasn't being nice. So I responded by showing why I didn't feel the need to be nice and provided my reasoning for it. Since it seems to be too much trouble, here is the post I'm getting the "imaginary" quotes you refer to from: https://news.ycombinator.com/item?id=14544002 https://news.ycombinator.com/item?id=14544002
- eropple 9y agoYou can point out how people are wrong and people won't have a problem with your posts. Be a jerk about it and people will. Hacker News, for its (many) faults, doesn't ascribe to the "you can be a sneering asshole but if you're Right you're Right". It's very possible to be both right and a jerk. It's incumbent upon you to avoid being a jerk or to not whine when people don't like jerks. This is basic-functioning-person stuff.
- sqeaky 9y agoI don't know who is right or wrong. I am a software developer and familiar with Unix/Linux. I actively try to be well informed about other topics related to this. When engineering I actively try to remain emotionally dispassionate. I understand what the argument is about and I see how in a technical sense either side could be "correct" here. Despite all that, the level of vitriol and defensiveness you have demonstrated makes me want to agree with everyone else. I am curious what the opinions are of people less informed on this topic and more emotionally in touch. You damage your side of the argument, not with your content, but your portrayal of the content. Some of the things you said have merit, but they are ignored and derided because they are attached to you and you are attached to vitriol and vitriol rightly gets ignored and derided. The best thing you can do for anything resembling your side of the argument is to just back down. If you don't say anything for a day or two it will all just blow over and you can try again later when people are more willing to listen. You can try approaching the conversation like an engineering problem and perhaps see that manners and politeness are to conversation as lubricant is to an engine (or perhaps high clocks speeds to software). You can have a conversation without manners, run an engine without oil or run software on low clocking parts, but it won't turn out as well as it could have.
- tomhoward 9y ago> Seriously, is HN fostering a culture where it's OK to spew pseudo-intellectual garbage as long as you're being nice? Not at all. It's fine and encouraged to correct or contradict someone. It's not OK to be personally abusive when you do it. The civility guideline has been in place since the very beginning of HN, and it's one of the biggest reasons why people keep coming back. The commenter was just recounting their own recollection. There's no need to be combative. If they're wrong, just point it out politely. No big deal.
- peterwwillis 9y agoThe commenter was not being combative or abusive in any way. They did point out the other person was wrong politely. They still got downvoted to hell. People don't come to HN for civility. They come because they can be smug polite idiots around other smug polite idiots and "the rules" protect and enforce this behavior. If you don't believe that disproving something stupid is hard, I give you Donald Trump. Sometimes you just need to speak out against stupidity without providing a groveling mathematical proof.
- tomhoward 9y agoA cursory glance at that commenter's recent history shows little evidence of politeness or intention to be polite. You don't have to like this community but surely you have better things to do than making it worse by trashing it like this? Also, invoking US politics drama to score points in this discussion topic shows quite a lack of sense of proportion. We are talking about a single person's casually-communicated recollections of their past experiences with a computer operating system. It really isn't worth getting wound up about.
- mikeash 9y ago"obviously incorrect" You admit that you don't have enough details to know exactly what they're referring to, yet you're confident enough to call their personal experience "obviously incorrect"? It's not an argument, it's an explanation based on personal past experience. You can't find any evidence, and you don't need to, because the claim being made won't influence how you do things today anyway. People's personal experiences can be interesting, and that adds to the conversation. Your overwrought criticism adds nothing. Kindly stop.
- fredmorcos 9y ago> You admit that you don't have enough details to know exactly what they're referring to, yet you're confident enough to call their personal experience "obviously incorrect"? I didn't admit to not having enough details. You have two tools: 1. Reasoning about the abstractions and implementations of how yes and /dev/zero work: the claims become obviously incorrect, even their own tests later in the thread show that on a "modern system". 2. Actually running the tests they claim (which would prove them correct): no freaking way to do that. Even they do not offer any numbers to back their own claims because everything in the argument is a maybe or a remember or a might or a may have. > People's personal experiences can be interesting, and that adds to the conversation. People claiming their personal experiences are fact without proving anything is hugely problematic. Remember that woman claiming her child got autism due to vaccines? Remember that US president claiming a child got autism due to vaccines? I remember seeing the earth as flat when I was working as an astronaut on the ISS. Go check my "personal experiences". I hope you see what I'm trying to convey here.
- mikeash 9y agoI really don't see how it's "obviously incorrect" when yes only needs to make system calls for writing, whereas /dev/zero needs to make system calls for both reading and writing. Furthermore you're assuming that both are highly optimized, whereas it's entirely conceivable that /dev/zero is less optimized. If what you're trying to convey is that abstract reasoning based on fundamental principles without any consideration of real-world complications is a superior approach to determining what's true, well, I reject that.
- acdha 9y ago> Seriously, is HN fostering a culture where it's OK to spew pseudo-intellectual garbage as long as you're being nice? The comment I called out had no technical content, argument, etc. and was only an attack on someone's credibility. That contributes nothing of value and in my book is worse than “pseudo-intellectual” because it's not even trying to contribute anything other than noise to the conversation. You would not be getting such intense negative reaction if your comment had been “Do you recall which operating system that was?” or “How long ago was that?”. That's how an actual engineering conversation should go, especially in a field such a long history of people uncovering unexpected performance issues caused by unintended consequences. As a simple example: in the early 2000s, a colleague reported that tools like grep and wc were running slower than our storage. That seemed odd since those are usually considered fast and certainly hadn't had that problem years earlier but a little testing confirmed that the switch to assuming Unicode by default had made a previously unoptimized code path the default and I'm sure the person who did that had assumed that someone would have noticed if code which had been shipped for years was that slow. The fact that for many years before and after you could mentally bucket those Unix shell tools into the “fast” bucket didn't change the fact that there was a multi-year period where you had to check. I have no reason to doubt that joosters' reported experience actually happened, especially given how rocky the 90s Unix world was. That was back when you couldn't even rely on a vendor's own C compiler not producing pathologically bad code. Someone having a /dev/zero implementation which triggered extra or slow kernel transitions, unnecessary access checks or audit logging, etc. would be disappointing but far from shocking[1]. More to the point, what do you hope to gain from such an unnecessarily combative style? You're not preventing any bad outcome, helping yourself or others improve, or otherwise doing anything other than lowering the level of discourse here. 1. Here's an example from 2012(!): https://groups.google.com/forum/#!topic/minix3/M3fjpvvOkuY https://groups.google.com/forum/#!topic/minix3/M3fjpvvOkuY
- deleted 9y ago[deleted]
- sillysaurus3 9y agoI think this subthread is a good example of what can happen if we quote the guidelines without context. It's a counter-intuitive trap I've also fallen into, so I wanted to mention it. In this case, this subthread could've been nipped by mentioning that it's ok to be abrasive to an extent as long as it's followed by a substantive comment. It's not diplomatic, but it's not against the rules. The guidelines are the framework the community is built around. They're not sufficient to explain why the community is built around them. (We probably wouldn't want the guidelines to be so complete, either. It's better to explain the motivations on a case-by-case basis.)
- acdha 9y agoIt's a valid question but looking at his posting history doesn't convince me that there's a way to word things which would result in a more productive response. Note that I lead with the observation that there wasn't anything to his post other than the attack — I don't think there's too much more to say about that before hitting diminishing returns.
- sillysaurus3 9y agoIt's a valid question but looking at his posting history doesn't convince me that there's a way to word things which would result in a more productive response. You could be right. But if you were in their shoes, you'd want to be given the benefit of the doubt.