Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!purdue!haven!mimsy!jogger.cs.umd.edu!straub
From: straub@jogger.cs.umd.edu (Pablo A. Straub)
Newsgroups: comp.software-eng
Subject: Re: Effort estimation based on language
Message-ID: <29986@mimsy.umd.edu>
Date: 7 Feb 91 16:03:31 GMT
References: <1900@blackbird.afit.af.mil> <7790001@hpwrce.HP.COM>
Sender: news@mimsy.umd.edu
Reply-To: straub@jogger.cs.umd.edu (Pablo A. Straub)
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 13

In <7790001@hpwrce.HP.COM> Kingsley Morse (kingsley@hpwrce.HP.COM) writes:
>
>My understanding is that APL is the most productive language to use.
>However, it's hard to read, so the learning curve is long and steep.
>I remember a study by IBM showing that applications can be developed
>4 - 10 times faster with APL.

Development time is usually not the main cost (especially  if  you  only
consider coding).  Maintenance is usually the main cost, and readability
is crucial there.  Besides, if I cannot read the code I can barely trust
it.

Pablo Straub, straub@cs.umd.edu