Xref: utzoo comp.windows.x:25679 comp.windows.news:2292 comp.windows.misc:1567
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!usc!apple!bbn.com!diamond.bbn.com!mlandau
From: mlandau@bbn.com (Matthew Landau)
Newsgroups: comp.windows.x,comp.windows.news,comp.windows.misc
Subject: Re: Open Windows 2.0 released (Sun press release)
Message-ID: <14411@garnet.BBN.COM>
Date: 14 Aug 90 00:22:14 GMT
References: <11722@hoptoad.uucp> <1990Aug2.025858.14871@brolga.cc.uq.oz.au> <4057@trantor.harris-atd.com> <1990Aug13.200849.22157@elroy.jpl.nasa.gov>
Organization: BBN Systems and Technologies Corporation, Cambridge, MA
Lines: 24

alan@cogswell.Jpl.Nasa.Gov (Alan S. Mazer) writes:
>Unless OW 2.0 is substantially improved in capabilities as well as speed from
>OW 1.0, some SunView code will not run.  

Ah, but it IS substantially improved, in almost every respect.  

I've been running OWN 2.0 on my Sparcstation for a week, and found it 
quite impressive.  It's very fast, it's at least as robust as any other
vendor's X11 implementation (and much moreso than either DECWindows or 
AIXWindows, in my experience), and it's obvious that a lot of work has 
gone into the desktop tools.  

In fact, it's the first X-based environment that's good enough to 
convince me to ditch SunView once and for all.

I've also run *many* different SunView programs, including some large
(3 MB) applications that tweak colormap segments, interact with the
window mangement functions on their own, use fullscreen access, and 
do other things you might expect to be broken under OWN.  Except for 
the well-documented "SunView windows always sit on top of the OWN 
display" problem, every single one of them has run flawlessly.
--
 Matt Landau		    		Rebel without a clue.
 mlandau@bbn.com