| |||||||||||||
VERY bad ideaVERY bad ideaPosted May 27, 2008 21:33 UTC (Tue) by khim (subscriber, #9252)In reply to: Another regression by dskoll Parent article: Fsyncers and curveballs (the Firefox 3 fsync() problem)
Anyway... even if CUPS is busted, Firefox should at a minimum offer to produce a Postscript file. To make it happen you need to keep the whole another printing library around. That's Windows way: sure with Windows NT core it's easy, but Windows95 it's still popular so let's use old library. And then plug new one in old if we need some effects. Then and patches to fix gotchas and another patches to fix problem introduced by patches. Then 10 years down the road you need 2GB or RAM and two cores just to print two pages of text. Not a good idea. May be it was to early to switch to gtk-print, may be not (after all Firefox is not released yet and may be Debian will manage to ship another release before that happens), but to have TWO print subsystems is just crazy.
(Log in to post comments)
|
|||||||||||||