X sucks (was: Re: Ware Ware Wizardjin)

[Steven J. Dovich; x272]

Let's not ignore our history here...

PostScript does not pre-date image processing technology. And the
imaging model used by X is the same one used by the bulk of image
processing and synthesis algorithms. Hence that code (and user base)
benefits most from the X imaging model and not the PostScript one.

PostScript provides an abstraction. That is usually a good thing. Not
every situation calls for the same abstractions. The real trick is
knowing the limitations of each of the relevant abstractions. 

To paraphrase the old Mounds candy bar commercial...

	Sometimes you feel like PostScript...  and sometimes you
	don't.

Should all applications pay because some might benefit? And to tie
this point back into the original discussion, how would using the
PostScript imaging model contribute to reducing the cost penalties of
software? Or would it encourage the proliferation of applications that
ignore the cost of computing resources they consume?



--
Steven J. Dovich <dovich at cadence.com>
                                       Cadence Design Systems/ACAE Div.
                                       2 Lowell Research Center Dr
Phone: (508) 934-0272                  Lowell, MA  01852-4995