Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!well!mitsu
From: mitsu@well.UUCP (Mitsuharu Hadeishi)
Newsgroups: comp.sys.next
Subject: Re: What's coming?
Summary: NeXTStep Shortcomings
Message-ID: <12330@well.UUCP>
Date: 23 Jun 89 01:08:29 GMT
References: <3898@tank.uchicago.edu>
Reply-To: mitsu@well.UUCP (Mitsuharu Hadeishi)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 20


	I work at Electronic Arts where we've been developing
state-of-the-art development environments for multiple targets
including optical media.  I had a chance to take a look at NeXTStep 0.8
a few months ago and was impressed with the completeness of the user-
interface toolkit and editor.  However, I was less than wowed by the
lack of structured code editors, lack of integration between the
user-interface editor and code editors, and the fact that all code
has to be COMPILED to be tested (except for UI hookups).  Are these
shortcomings going to be addressed in future versions of the system?
Here at Electronic Arts we've developed a portable object-oriented
development environment that allows instant turnaround on interpreted
code, arbitrary mixing of compiled and interpreted code, etc.  This
facilitates debugging considerably because all time-critical code
can be compiled while you're editing interpreted code with zero
debug turnaround---the best of both worlds.  We also have at least
minimal structured editing with instant syntax checking for interpreted
code; we don't have to use vi to edit our source.  Is NeXT planning
to add any of these features to address the shortcomings of its
development environment?