Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!newstand.syr.edu!news.maxwell.syr.edu!news.enteract.com!news.he.net!news.cichlid.com!news.scruz.net!cruzio.com!news
From: jordan@cruzio.com (Jordan Bortz)
Subject: Re: It aint the *LANGUAGE* Silly!!
X-Newsreader: Forte Free Agent 1.0.82
Reply-To: jordan@cruzio.com
Sender: news@cruzio.com (System Administrator)
Organization: Object Productions Inc
Message-ID: <E5K39B.8L1@cruzio.com>
References: <E554n2.C9w@cruzio.com> <3302a602.47160004@news.ozemail.com.au> <01bc19b8$9768b5b0$ed22109b@russ-mc-laptop>
X-Nntp-Posting-Host: mbay5.cruzio.com
Date: Thu, 13 Feb 1997 16:19:41 GMT
Lines: 41

"Russ McClelland" <russmc@netbox.com> wrote:

>You write this as though there are no versions of Smalltalk that have
>wizards (Smalltalk MT), can support OLE (Smalltalk MT), use OCX controls
>(Smalltalk MT), easily support ODBC (Smalltalk MT), support native
>multithreaded development (Smalltalk MT), or have a small footprint
>(Smalltalk MT), and doesn't cost a million bucks(Smalltalk MT).

Well, although Smalltalk MT may have lots of exciting technology, its
sure not being hawked by a major vendor, and that in itself is a huge
issue for big corporate customers, and even not so big ones...The fact
that only one Smalltalk has these critical features is, in itself, a
little scary..

 

>Anyone who thinks it would take 10 weeks to create a simple document editor
>in Smalltalk is nuts!  All I'd have to do is reuse the document editor that
>comes with Smalltalk.  Done!! In less than an hour or two.

I think getting print preview would take 10 weeks in itself, unless MT
has that capability..
>> 
>> Tell me again why you want to use Smalltalk."

>Try developing a large scale application in C++ where you have to worry
>about memory management with a large number of classes, you'd see why we
>want to use Smalltalk.  Most large C++ systems end up using tools to make
>C++ more like Smalltalk (ie reference counting smart pointers, auto
>pointers, classes as first class objects, etc. )
>-- 

I have to agree with you that programming in C++ is an excersize in
frustration...but my original post had to do with envirionments being
a container for components -- if the components are good, then the
user merely has to do a lot of property setting...effectively hiding
the environment anyway.

	Jordan


