> strong ego-driven component. This leads to several undesirable symptoms.
> One, as you have noticed, is a tendency to overlook (if not downright
> ignore) certain sections of the (potential) user community; "If I don't
> need this, then I don't see why anybody else should, either". Another
> is the culture of contempt for Microsoft; some otherwise useful pieces
> of software (MySQL is one that comes to mind) go out of their way to
> make themselves less attractive to users of Microsoft software (and,
> to a lesser extent, adherents to other standards that the primary
> author of the software in question doesn't care for). Both of these
> problems show up in dcraw, to name an example more familiar to many
> of us. And, of course, there's the general user-unfriendliness of
> other useful pieces of software such as Vuescan.
>
I'm assuming you're referring to the dcraw author's position of
vehemently NOT including JPG support into dcraw. There are historic
rationale for that sort of thinking... not just arrogance or
anti-Microsoft sentiment. In the traditional unix world, a utility was
meant for function first... it did one thing, and it did it very well.
The purpose of dcraw in this light is to do the RAW->RGB conversion.
Converting to JPG can be done with dozens of other utilities painlessly...
no point in cluttering up the code.
... but yes, there is often ego involved. Fortunately the code is
there if one wanted to hack it up. If it's well-written modifications,
they should be accepted into the original project.
-Cory
--
*************************************************************************
* Cory Papenfuss, Ph.D., PPSEL-IA *
* Electrical Engineering *
* Virginia Polytechnic Institute and State University *
*************************************************************************
--
PDML Pentax-Discuss Mail List
[email protected]
http://pdml.net/mailman/listinfo/pdml_pdml.net
