The end of LWN comment dialog?
The end of LWN comment dialog?
Posted Apr 1, 2009 5:31 UTC (Wed) by ncm (guest, #165)In reply to: That massive filesystem thread by ajross
Parent article: That massive filesystem thread
Posted Apr 1, 2009 6:07 UTC (Wed)
by bojan (subscriber, #14302)
[Link] (7 responses)
What exactly is not polite about that? Is sarcasm now verboten on LWN? I see plenty of it. Daily.
In a post not so long ago, someone accused me of hiding behind Ted's authority (although I actually used documentation to support my case - which many don't bother to read, of course). This time, I point out what to me is nonsense coming from an even bigger authority, but that's no good either. I'm not sure what position of mine would satisfy fragile sensibilities here. Only silence, I guess.
This time I was being accused of making snide remarks. So, I replied to ajross using his terminology, although I do not actually agree with that qualification (which you can see from my sarcastic: "see, being snide again" remark) and I should have used "so called snideness" in my reply instead. I am really just being sarcastic, because we are all supposed to rally behind the high priest or something.
Sure, Linus is a genius, but that doesn't mean that whatever he says is beyond criticism. And, I do not see how I am not being polite by exercising criticism with a hint of sarcasm.
What is it exactly that you have the issue with in my posts? What exactly is impolite?
Posted Apr 1, 2009 7:54 UTC (Wed)
by khim (subscriber, #9252)
[Link] (3 responses)
Nope. You are being 100% smart-ass. Linus's reality check is not
inconsistent. It's description of reality and reality is not
consistent. Whenever it was? You have different factors and in
different but quite real situations different factors prevail. That's different facet of reality. When you consider reality from kernel
developer POV what the applications are doing is your "unchangeable fact",
your "speed of light", when you consider reality from application developer
POV what the kernel does is "unchangeable fact" and you should deal with
it. This is true even if kernel developer and application developer is the
same person. You can only think differently if your application is designed
to only be used "in-house" and you can always guarantee
control over both kernel and userspace - and git was not designed to only
be used "in-house"... You are exercising ignorance with a hint of sarcasm. That's
different.
Posted Apr 1, 2009 8:29 UTC (Wed)
by bojan (subscriber, #14302)
[Link] (2 responses)
Let me review.
When another Unix kernel (or Linux) holds your data in buffers and commits metadata only (because it is allowed to), you, as an application developer, deal with it by ignoring that fact.
And, when your file system does crazy things with the perfectly good system call, you also ignore it as a kernel developer.
WOW, is that now the new "very special relativity"? We pick whichever behaviour is the most narrow to a specific file system and go with that?
Posted Apr 1, 2009 14:22 UTC (Wed)
by drag (guest, #31333)
[Link] (1 responses)
POSIX allows you never to write data to disk at all. That will make your file system very fast. After all you can have a POSIX-compliant file system that operates off of ramdisk quite easily.
POSIX file system access is designed to describe the interface layer between userland and the file system. It leaves the actual integration between the file system and the hardware, as well as the internals to the file system itself is left up to the developer of the OS.
It is like if you discovered all of a sudden a network service provided by a Apache-based web app uses SSL badly so that all usernames and passwords are transmitted over the Web in plain text... then you complain about it and the developer says back to you that his application's behavior is allowed by TCP/HTTP/SSL and that you should be changing your password with each usage, like people who use his app correctly do. Then he emails you some documentation from a security expert that says you should change your password frequently and that many other protocols like telnet or ftp send your username and password over the network in plain text.
Posted Apr 1, 2009 16:10 UTC (Wed)
by foom (subscriber, #14868)
[Link]
Posted Apr 2, 2009 23:17 UTC (Thu)
by xoddam (guest, #2322)
[Link] (1 responses)
I plead guilty and I apologise. That was immediately after replying to someone else's post the gist of which was "Ted wrote ext2 and ext3 in the first place, he is therefore above criticism." It concluded with the words "Know your place", which got me riled.
[proverb: in the midst of great anger, never answer anyone's letter]
Your words were not so condescending but they had much the same emphasis: all ur filesystems are belong to POSIX (not users) 'cos POSIX is the law, and by the way Ted's interpretation is the only correct one because he's the primary implementor.
I hope you understand where I was coming from. Forgive me.
Posted Apr 2, 2009 23:56 UTC (Thu)
by bojan (subscriber, #14302)
[Link]
Posted Apr 8, 2009 0:05 UTC (Wed)
by jschrod (subscriber, #1646)
[Link]
But your self-rightousness doesn't allow to understand this, obviously. Luckily, there are still some discussion threads where you don't try to take over. I hope the likes of you will remain few on LWN in the future, this is not Slashdot, after all.
Posted Apr 1, 2009 15:46 UTC (Wed)
by GreyWizard (guest, #1026)
[Link] (7 responses)
People get nasty in the comments here all the time. If there's something beautiful and fragile here it's already in a thousand jagged pieces. But people hector one another about being polite all the time too. That also wrecks the signal-to-noise ratio and solves nothing.
Posted Apr 4, 2009 9:05 UTC (Sat)
by jospoortvliet (guest, #33164)
[Link] (6 responses)
Living in a country where that mode of thinking is the norm, I can tell
A little decency now and then doesn't hurt. I know people who, knowing how
Posted Apr 5, 2009 3:34 UTC (Sun)
by GreyWizard (guest, #1026)
[Link] (5 responses)
But saying "be polite you jerk" merely drags things even further down into the muck.
Posted Apr 5, 2009 12:43 UTC (Sun)
by jospoortvliet (guest, #33164)
[Link] (4 responses)
First of all, some people don't notice their behavior is unnecessarily impolite. Pointing it out can help them (if they are willing to be reasonable in the first place). Never pointing out somebodies failures will make them fail forever.
Second, it shows you care about being polite. If others show they care too, a culture of 'you should be polite' can be maintained. As you might have noticed from the differences between FOSS communities, culture is important and heavily influential. And it can be changed.
Some things to note:
Posted Apr 5, 2009 15:42 UTC (Sun)
by GreyWizard (guest, #1026)
[Link] (3 responses)
A truly polite request for more courtesy might help but it's difficult to be sure because such things are quite rare. Giving in to the temptation to scold even just a little makes the comment worse than useless. Unless you are absolutely certain you can do it right it's better to focus on substantive issues and avoid appointing yourself a courtesy cop.
Posted Apr 5, 2009 16:20 UTC (Sun)
by jospoortvliet (guest, #33164)
[Link] (2 responses)
Posted Apr 5, 2009 16:27 UTC (Sun)
by GreyWizard (guest, #1026)
[Link] (1 responses)
Posted Apr 5, 2009 17:11 UTC (Sun)
by jospoortvliet (guest, #33164)
[Link]
On re-reading the thread, I think you are right in that ajross was more impolite than bojan, which often leads to a downward spiral and isn't helpful... bojan's post wasn't that far off from the normal tone on this site.
Anyway. This is went pretty far off-topic, and I think we mostly agree. For as far as we don't, we at least agree on that ;-)
The end of LWN comment dialog?
Yup. It's the beginning of the end.
If you read my original post in this thread, you will find that
I am pointing at inconsistencies of what Linus describes as reality
check.
So, I ridicule (among other things) his conclusion that: ext3
sucks at doing fsync(), hence we should drop fsync().
And, I do not see how I am not being polite by exercising
criticism with a hint of sarcasm.
Yup. It's the beginning of the end.
Yup. It's the beginning of the end.
Yup. It's the beginning of the end.
of the other article's threads. I'd like to suggest that it might be in everyone's interest to move on to
more useful pass-times than rehashing the same arguments over and over again every time there's
an update on the subject.
sticks & stones
sticks & stones
The end of LWN comment dialog?
The end of LWN comment dialog?
The end of LWN comment dialog?
with what comes out, it's on their own plate.
you it also has disadvantages... If only because the resulted hurt
feelings can muddy the discussion more than you might think. Besides, it
chases people away who would otherwise have contributed constructively -
it's not acceptable behavior in all cultures. Ever wondered why the FOSS
community is still predominantly western, despite many smart developers in
countries like India?
blunt they can be, ask someone else to read certain emails before sending
them. After all, reality is that people DO have feelings.
The end of LWN comment dialog?
The end of LWN comment dialog?
- people DO care about what others think of them. No matter how much they scream 'no I don't', they do. It is our nature.
- people should know their arguments are not supported by being mean - it is the other way around.
- I agree that a 'be polite you yerk' might not always be the best way to correct someone. A personal mail can do more. However, it won't show up in public (unless an apology is made), thus it does not much to influence others who might think it is acceptable behavior because the guy got away with it. Of course, giving a good example is better than anything else.
- Of course discussing without end whether somebody was polite enough or not muddies the discussion and lowers the SNR.
The end of LWN comment dialog?
The end of LWN comment dialog?
The end of LWN comment dialog?
The end of LWN comment dialog?