Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!ucsd!ucbvax!agate!eris.berkeley.edu!doug
From: doug@eris.berkeley.edu (Doug Merritt)
Newsgroups: comp.sys.next
Subject: Re: XWindows W11 Release 4
Summary: Why the world needs X on NeXT
Message-ID: <1990Sep20.145725.22035@agate.berkeley.edu>
Date: 20 Sep 90 14:57:25 GMT
References: <2241@opus.cs.mcgill.ca> <92180@srcsip.UUCP> <OLSON.90Sep19122115@sax.cs.uiuc.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 19

In article <OLSON.90Sep19122115@sax.cs.uiuc.edu> olson@sax.cs.uiuc.edu (Bob Olson) writes:
>There are those of us who are great fans of the NeXT, [...] but who have
>to do project development using X for the work they get paid for :-).

Similarly, my company must support several hardware platforms so that
our software will run on the customer's machines. X gives us a way to
develop just one piece of software, rather than writing brand new software
for each target platform's windowing system, saving mucho time and money.
Naturally we need to have X on our development machines.

Once X is available for NeXT, I can make a case for using NeXT as
our development system. Until then, there's nothing I can say,
and we just keeping buying more Sparcs.

As usual, compatibility in one form or another turns out to be the
overriding concern in the real world.
	Doug
	Doug Merritt		doug@eris.berkeley.edu (ucbvax!eris!doug)
			or	uunet.uu.net!crossck!dougm