3 ms·
> 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 technica
by 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