Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!elroy.jpl.nasa.gov!aero-c!gumby.dsd.trw.com!deneva!news
From: thomsen@spf.trw.com (Mark R. Thomsen)
Newsgroups: comp.lang.objective-c
Subject: Re: Health of Stepstone and ObjC
Message-ID: <283C3D20.6BF7@deneva.sdd.trw.com>
Date: 23 May 91 22:07:28 GMT
References: <1991May23.075820.983@agate.berkeley.edu>
Sender: news@deneva.sdd.trw.com
Organization: TRW Inc., Redondo Beach, CA
Lines: 23

Izumi Ohzawa writes
  How critical is Stepstone's continued operation to NeXT and NeXT
  users?
  
  What part of NeXT software is directly dependent on Stepstone?
  

Stepstone is not a critical component to NeXT in the sense a) NeXT
only uses OC and not IC-Pak and b) NeXT liscences OC but did the
critical parts of the compiler themselves (apparent from the
trademarking). NeXT selected OC at the time because dynamic
binding was there ... C++ was not there yet. However it looks
like C++ could become the 'native language' easily for NeXT.

Afterall, they are selling NeXT computers and not Objective-C
computers.

Personally I would hate to see OC and Stepstone go under. My
people really prefer OC to C++, and so do I. Stepstone was
good to work with when we used their products on Sun, and the
product worked well.

Mark R. Thomsen