2009-10-26 22:30:20 UTC
Well, the point is rather not what you were saying but how you were expressing it :
"Despite this knowledge and awareness, reading the following lines
in TriMeshViewer.java has simply left me stunned[]
Oh, and brace yourself for when you figure it out. []
When I came to my senses, the obvious questioned immediately popped up"
Etc.
This is not exactly what I'd call a nice comment (and not an objective one either). Pinpointing one's code deficiencies is something people are usually happy of because it helps improve their code. Suggesting their code is grossly flawed is something entirely different. This is true of any situation when you have to say to someone he is wrong. Plainly saying "you're wrong" may work with people ready to accept they're wrong (and they're aren't that many of them). Saying "you're so wrong I was stunned" will generally not work even with the above category because people will perceive that as an unnecessary aggression, which it is.
So the "I don't want to read this" doesn't target your technical statements but the aggressive way (or so perceived) of expressing them. And since this project is open source based on people's good will, we also have the choice of ignoring aggressive technical statements. This may seem unfair or unjustified, but we want to have fun. Otherwise, it will end up just like our day jobs.
To keep going forward, I would suggest you keep expressing your comments in a neutral, objective way. We'll get used to each other way of saying things and hopefully avoid misunderstandings.
Francois.
