Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!kazim
From: kazim@Apple.COM (Alex Kazim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Comm Toolbox questions
Summary: What can I say...
Keywords: APDA Communications Toolbox Ethernet Macintosh UNIX
Message-ID: <34760@apple.Apple.COM>
Date: 15 Sep 89 21:21:45 GMT
References: <627@daitc.daitc.mil> <34737@apple.Apple.COM> <1989Sep15.135231.3726@ux1.cso.uiuc.edu>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 32

In article <1989Sep15.135231.3726@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes:
>
>I find it disappointing (not to mention ironic) that both the Communications
>Toolbox and MacTCP are Apple products, but Apple thinks that third parties
>should provide the software necessary to tie them together.
>

Let's step back and look at some of the reasons:

1) Resources: Sometimes we just don't have the people to work on
a needed product.

2) Evangelism: tool development is a marketplace for developers.  Apple
is in the business of empowering and leveraging 3rd parties.  The
initial tools released in the CommToolbox will be the minimal that
we can both show the power and utility of the toolbox.

3) Marketing:  We are a hardware company -- it's where we make our
money.  It's why we don't do applications anymore :-)

Let's face it: if we wrote it, a lot of people wouldn't consider doing
one because they think we have a lock on the market.  Apple came under
a lot of pressure to axe the free MacWrite & MacPaint. 

What I'm hoping is that we don't just see one of these tools, but 
a whole slew of: "hey, look what I hacked up over the weekend"

======================================================================
Alex Kazim, Apple Computer
Phone Repair Man
======================================================================