Yes, you are right, but criticism comes in two flavors constructive and 
disparaging. If you are offering constructive criticism your comments 
are welcome, but to offer nothing but disparaging remarks, which is all 
your first post offered, is shallow. These people (Mozilla programmers) 
are trying to produce something that will not only be useful, but that 
everyone will want to use due to it's quality of engineering and 
imaginative design. They make nothing from this other than the 
satisfaction that they have done something spectacular that helps 
others. For you or anyone else to come in and try to hold them to a 
deadline is not only wrong, but it is also shortsighted and childish.

I wasn't going to respond to this at first, hoping that the perpetrator 
would just be ignored and would eventually go away. I just couldn't take 
it any more and felt I needed to state my piece. I'm sorry to everyone 
else for taking up your time and resources.

Petrus Lundqvist wrote:

>> But is the criticism valuable when it is nonspecific? Does it change the
>> position of the sun to criticize a clock for being an hour off? In what
>> way does your critical comment in any way help the project? In no way.
>> It is worthless because it can change nothing and offers no value to the
>> project.
> 
> 
> I wasn't the one with the critical comment. I was just saying that just
> because you "can't do better" doesn't mean you can't comment. Example: I
> can't make a skin for Mozilla but I do have LOTS of ideas and comments on
> the current ones. If I write a long post about how to improve a skin or
> even if I take the tone of "hey, this sucks.. this should be fixed!", it
> shouldn't trigger "shut up or make a better one yourself" comments. It 
> should be received as any feedback from anyone - participating in working
> on the project or not. Participation is not what makes a comment valid or
> not.
> 
> Peppe


-- 

ICQ - 77808395

Reply via email to