3 ms·
> May I suggest you withdraw from this line of argument? May I suggest that you look at the paper in question and realize it is one that requires careful and u
by nknighthb 13y ago
> May I suggest you withdraw from this line of argument?
May I suggest that you look at the paper in question and realize it is one that requires careful and uninterrupted attention for an extended period of time to properly understand?
May I also suggest that you not make assumptions as to what another person is or is not doing, and how it may interfere with their ability to do some things but not others?
Or would you rather just be a judgmental, holier-than-thou asshole?
- tptacek 13y agoAs a reminder, this is what you said upthread: My conclusion is that his application-level networking experience has fooled him into thinking he knows more than he does about actual network architecture, management, and performance issues. Or maybe he doesn't realize the issues even exist. My conclusion is that you made that comment having absolutely no idea what my experience was, and then decided to get pissy when the facts didn't line up with your bet. I've made the same dumb bet on HN a bunch of times. "This is just some Ruby dork who knows fuck all about", I don't know, "tax law". It never works out for me, either. The thread is now full of technical commentary about the point I made. Lots of smart people disagree with me; no surprise! You've contributed none of that commentary. Maybe now's a good time to start? You seem to feel passionately about the issue.
- nknighthb 13y ago> you made that comment having absolutely no idea what my experience was I made the comment based on the fact that the only thing you ever talk about actually doing is security-related. On everything else, you just pontificate context-free. You implied earlier I should have looked at your "public linkedin profile". You should know that, for me, your profile contains nothing but your current and past employers, and your university. Nothing about what you did there. What was I supposed to conclude from that? I've spent most of my career working for companies that do video-related work, but if you ask me a question about MPEG transport streams, I'll refer you to the guy who, y'know, actually deals with MPEG. At this point I am pissy, yes, but that's not because I was wrong, it's because of the asshole who decided he knows better what my personal time commitments are than I do. > The thread is now full of technical commentary about the point I made. No, it isn't. The thread is full of cursory rejections of your equally cursory commentary. There is absolutely nothing interesting about any of it, because it's all surface bullshit that everybody already knows. There are no details. There's nothing concrete. There's nothing new. Boring, hand-wavy crap. Propose something concrete, something that actually addresses the obvious criticisms you already know are going to be leveled, and I might get interested. Right now, all I'm interested in is ignoring HN for a while.
- tptacek 13y agoWell, just to be clear: you were pretty wrong about what I've "done". Have a good weekend. Ignoring HN can definitely be a healthy thing sometimes.
- deleted 13y ago[deleted]