Newsgroups: comp.lang.python,comp.lang.tcl,comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!news.alpha.net!uwm.edu!lll-winken.llnl.gov!ames!cnn.nas.nasa.gov!cnn!rpeck
From: rpeck@java.nas.nasa.gov (Rodney C. Peck)
Subject: Re: Sun's plans about Tcl.
In-Reply-To: exukenc@exu.ericsson.com's message of Thu, 27 Oct 1994 13:45:56 GMT
Message-ID: <RPECK.94Oct27093601@java.nas.nasa.gov>
Sender: news@cnn.nas.nasa.gov (News Administrator)
Nntp-Posting-Host: java.nas.nasa.gov
Organization: NAS/NASA Ames Research Center
References: <9410240045.AA17925@mole.gnu.ai.mit.edu>
	<1994Oct27.134556.16993@exu.ericsson.se>
Date: Thu, 27 Oct 1994 16:36:01 GMT
Lines: 24
Xref: glinda.oz.cs.cmu.edu comp.lang.python:2258 comp.lang.tcl:20967 comp.lang.scheme:10707


   It's interesting to me that you decided to preempt their "attack"
   on scripting languages by making your own attack against anything that's
   not lisp/scheme oriented.

   The simple fact is that Sun will have very little more affect on which
   scripting languages get used than you will. Programmers will still 
   choose the language that they think in and are most comfortable with.

I don't agree with this -- the programmers will write in the language
that their company decides they should write in, except for the
relatively small number of people who are in a position to make that
choice for themselves.

My main point was to bring up Sun's previous two universal solutions
and hoped-to-be defacto standards:  Sunwindows and NeWS.  Both of
these have pretty much bit the dust even though Sun was heavily behind
them for quite some time.  And during that time, Sun was much more
influential than they are today.


--
Rodney

