comp.lang.ada
 help / color / mirror / Atom feed
From: dickey@ssc-vax.UUCP (Frederick J Dickey)
Subject: Thus spake the DoD...
Date: Fri, 15-Feb-85 09:34:18 EST	[thread overview]
Date: Fri Feb 15 09:34:18 1985
Message-ID: <423@ssc-vax.UUCP> (raw)

[gourmet line eater snacks: * * * * *]

The DoD has announced its intention to make Ada the single, common,
computer language for Defense mission-critical applications. Presumably,
this means that if you have a Defense mission-critical application of AI, 
then you're going to program it in Ada. Is this reasonable? Is this
possible? Now I happen to work in an AI group of a large aerospace
company located in the general vicinity of Seattle, WA, so the answers
to these questions are of considerable interest to me. What do people
out there on the net think about this? Should AI people rush out and 
buy Ada manuals? Sell their Symbolics stock? Roll over and play dead?
Or what?

To help get this discussion off the ground, I am including three
hypothetical responses to my questions. 

-------------------------------------------------------------------------
HYPOTHETICAL RESPONSES
-------------------------------------------------------------------------

[response from Byron Kapse: I do all my AI programming in Ada. Lisp is an 
archaic dinosaur from the 50's. Ada is the language of the 80's. It's the 
first non-von Neumann language. It results from years of research into 
concepts that encourage and enforce good programming practices. Ada is the 
basis for a new culture of software engineering. The AI community can
definitely benefit from the discipline that results from the use of Ada.
The DoD is well advised to mandate the use of Ada for embedded applications, 
including embedded AI applications.]

[response from John McCadr: No way the DoD is going to use Ada for AI; they're
out of their minds. Give me one example of a significant AI system written in
Ada. It's is a von Neumann nightmare! Using Ada is like trying to brush 
your teeth with a strait jacket on. If you paid Ada programmers 5 cents a line 
to code Ada, they'd become millionaires. The DoD is going to have to admit 
that Lisp is the only way to go. Modern Lisp environments represent over 
thirty years of experience. We know how to do it. A programmer at a Lisp 
workstation like a Symbolics or LMI can blow the socks off any Ada programmer 
alive.]

[response from John Q. Programmer: Why can't we have our cake and eat it too? 
I have a product specification for a Lisp that is based upon Ada. Apparently, 
what this product does is take Lisp source code and translate it into Ada. 
So if the DoD says "do it in Ada," all you have to do is show them the 
translated code and they'll be happy while you can do your coding in Lisp. 
Besides that, this product allows you to combine the symbolic processing 
capability of Lisp with the number crunching capability of Ada. You get 
the best of both worlds! This really looks like the way to go.]

             reply	other threads:[~1985-02-15 14:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1985-02-15 14:34 Frederick J Dickey [this message]
  -- strict thread matches above, loose matches on Subject: below --
1985-02-14 15:59 Thus spake the DoD Frederick J Dickey
1985-02-17  1:58 ` Robert Hofkin
1985-02-17 16:36 ` g-frank
1985-02-18  5:18   ` Skef Wholey
1985-02-18 14:33 ` Chuck Hedrick
1985-02-19 19:09   ` Daniel J. Salomon
1985-02-25 17:08     ` Jan Steinman
1985-02-26 23:20     ` Stanley Shebs
1985-02-27 19:22       ` Daniel J. Salomon
1985-03-01 19:30         ` Stanley Shebs
1985-03-01 20:13         ` neves
1985-03-02  4:33         ` Thomas M. Breuel
1985-03-06 14:13         ` geb
1985-02-28  3:16       ` David Schachter
1985-03-01 19:00         ` Stanley Shebs
1985-03-03  3:08         ` Joaquim Martillo
1985-03-03  6:12         ` T J Jardine
1985-03-05 16:55           ` Jan Steinman
1985-03-05 21:07           ` Robert A. Pease
1985-03-12  1:47           ` Ed Colbert
1985-02-18 23:49 ` M.Fischer
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox