TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding:
7bit
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Tom Moran <[log in to unmask]>
Date:
Tue, 14 Apr 1998 22:32:39 -0700
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Reply-To:
Parts/Attachments:
text/plain (13 lines)
Stanley Allen, in part of an excellent note, says that it is
"a mistake to sell Ada to programmers on the grounds that
...(reliability).  They want features and power."
  What might cause a programmer, when given a new assignment,
to say to his boss "Let's try Ada for this"?  What might
cause him to spend his own money on a book to learn something
about Ada, or to spend his own time to, say, download Gnat or
ObjectAda, and experiment?
  Imagine yourself one of the best programmers in your shop,
your boss and colleagues know it, and you feel confident in
your abilities in your current language.  What would cause
you to spend time and perhaps even money investigating Ada?

ATOM RSS1 RSS2