Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!nrl-cmf!cmcl2!husc6!bbn!rochester!cornell!uw-beaver!ssc-vax!benoni
From: benoni@ssc-vax.UUCP (Charles L Ditzel)
Newsgroups: comp.windows.news
Subject: Re: Display POSTSCRIPT to be available on DECwindows
Message-ID: <1626@ssc-vax.UUCP>
Date: 24 Jan 88 05:41:58 GMT
References: <8801210012.AA24025@ondine.LOCAL> <20499@teknowledge-vaxc.ARPA> <10486@jade.BBN.COM>
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 16
Summary: why bother?

In article <10486@jade.BBN.COM>, mlandau@bbn.com (Matt Landau) writes:
> In comp.windows.news, mkhaw@teknowledge-vaxc.ARPA (Mike Khaw) writes:
> >Does this mean that if DECWindows and/or Display Postscript catch on
> >Sun will be forced to announce a new "merged NeWS, X, Display Postscript"
> >to conform to de facto standards?
> 
> Well, since Display PostScript isn't a window server, that's not really
> what they'd have to do.  And given that Display PostScript is OUTPUT ONLY, 
...
why bother?  I guess I would be interested in knowing what Display 
Postscript can do that NeWS can't.  My understanding is that it is
forced to live in the native window system, single-tasking, no 
networking... is this correct?  I suppose the allure is if you use
X...but wouldn't this slow down X even more than it is now?

Any info would be appreciated.