Newsgroups: comp.lang.smalltalk,comp.lang.c++,comp.object
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.acsu.buffalo.edu!news.uoregon.edu!enews.sgi.com!news.sgi.com!news1.best.com!noos.hooked.net!news.scruz.net!cruzio.com!news
From: jordan@cruzio.com (Jordan Bortz)
Subject: Re: Language Neutral skillsets [was Re: Java Fission]
Reply-To: jordan@cruzio.com
Organization: Object Productions Inc
Date: Mon, 16 Sep 1996 16:13:43 GMT
Message-ID: <DxuAzs.E7r@cruzio.com>
X-Newsreader: Forte Free Agent 1.0.82
X-Nntp-Posting-Host: mbay5.cruzio.com
References: <321D94F2.73E0@concentric.net> <3220B964.58F8@terracom.net> <504ki4$3q4@news1.sympatico.ca> <323a414a.346750931@marine.jumppoint.com> <514u4r$o0m@hoho.quake.net>
Sender: news@cruzio.com (The News User)
Lines: 45
Xref: glinda.oz.cs.cmu.edu comp.lang.smalltalk:43515 comp.lang.c++:213245 comp.object:55735

billf@jovial.com (Bill Foote) wrote:

>In article <323a414a.346750931@marine.jumppoint.com>,
>Ian Upright <ian@peacesummit.com> wrote:
>>
>>So nothing in this world is a sure thing.  But what are the chances of
>>PPD dropping off the face of the planet?  This is a very serious
>>question for me, as pretty much, my life, and my current projects,
>>depend on PPD staying in business.  If PPD goes chapter 11, I'm in for
 
>Next two years?  I doubt it.

I wouldnt be so sure; as per them going BK - that may never happen.
But as far as Smalltalk being buried as a language --- I think that
big clients relying on Smalltalk will continue to use it, but new
projects will move to some kind of Java/RAD/DB environment.
I'm not sure I hear PPD elaboarting the "compelling reasons" for
sticking with VW, other than supposed platform independance, and the
fact that right now, VW still has, say, a 6-12month lead over Java in
terms of UI/DB integration.

>But why so worried?  IMHO, most of the important skills associated with
>"Smalltalk Development" transfer quite well to Java development.  There
>are a few language/environment differences that can change designs
>(like no block closures, static typing, and no extensive event model),
>but when it comes down to the fundamental task, the language is pretty
>much a detail.

There is cause for concern. For one, C++ programmers are also able to
make the transition to Java, and charge quite a bit less than
Smalltalk programmers.  There are also more C++ programmers, and they
are already familiar (many of them) with OLE/COM and ActiveX.

So the real problem is not will we be forced to program in Java --
Java is inherently not that bad language wise.

The problem is, will we make the rates we are accustomed to
programming in Java?

	Jordan

 Smalltalk Consultant

 

