Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 27 May 2005 21:29:54 -0700
From: Edward Peschko <esp5 AT pge DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Serious performance problems (malloc related?)
Message-ID: <20050528042954.GA4196@venus>
References: <4297A14B DOT 9070409 AT plausible DOT org> <20050527234027 DOT GA7522 AT trixie DOT casa DOT cgf DOT cx> <4297B572 DOT 9050200 AT plausible DOT org> <20050528005054 DOT GB7522 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050528005054.GB7522@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

On Fri, May 27, 2005 at 08:50:54PM -0400, Christopher Faylor wrote:
> On Fri, May 27, 2005 at 05:04:02PM -0700, Andy Ross wrote:
> >Christopher Faylor quipped:
> >> It seems pretty clear to me that if this is a really serious problem
> >> for you then the best way to get it fixed is to gain more than zero
> >> knowledge of cygwin.
> >
> >Gee, thanks.  Very helpful.  Can you at least type the commands in and
> >verify the problem for me before you get snippy?  I said "zero
> >knowlege" in an attempt to be modest*, but if you really want to get
> >into a tussle about developer credentials, I'm happy to oblige.
> >
> >* I mean, come on: it's a 20 line program that shows a 15x performance
> >  regression in a real-life, non-trivial application
> >  (http://www.flightgear.org), takes all of 5 commands to verify that
> >  can be copied right out of the source code, and even comes with a
> >  (IMHO) pretty insightful guess as to where the problem might lie.
> >  Most developers have erotic fantasies about this kind of bug report.
> 
> Gee, I'm sorry you thought I was being "snippy".  You apparently missed
> that I was just providing you with some obvious advice.
> 
> You state that this is a "rather serious problem".  It seems like if this
> was a really serious problem you'd be actively working towards solving it
> rather than sending out email and hoping to get lucky.  If you think it
> is malloc that is causing the problem then instrumenting malloc to prove
> your assertion is not that much work.  Building the dll is probably not
> five commands but it is not a heck of a lot more than that.
> 

But Mr. Faylor, no offense, but you *are* snippy. You complain about 
lack of clue in bug reports, lack of motivation for people to pick up the 
code and play with it, yet you *constantly* throw cold water on 
people's motivation to feel good about dealing with cygwin.

Just some advice - take a step back and get a good meta-view at yourself.

You could seriously use a huge helping of your own advice and fix
the issue of people complaining about your attitude. 

There are two ways of seeing it - everybody (or a huge subset of everybody) 
is wrong and I'm squeaky clean, or yes I could improve my attitude in how
to deal with people. 

I know this cultural issue has deterred me in the past; I keep hoping that 
things'll change and I (and possibly many others) would change their mind
and start assisting cygwin.


Ed

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/