From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.ada Subject: Re: If not Ada, what else... Date: Tue, 28 Jul 2015 00:22:16 -0700 Organization: A noiseless patient Spider Message-ID: <87lhe0px07.fsf@jester.gateway.sonic.net> References: <87k2u96jms.fsf@jester.gateway.sonic.net> <06f8a6f9-d219-4d40-b9ac-8518e93839bd@googlegroups.com> <87y4io63jy.fsf@jester.gateway.sonic.net> <7a29d3e9-d1bd-4f4a-b1a6-14d3e1a83a4d@googlegroups.com> <87mvz36fen.fsf@jester.gateway.sonic.net> <2215b44f-8a89-47c6-a4c4-52b74d2dac45@googlegroups.com> <9e492c82-868d-43d3-a18a-38274400e337@googlegroups.com> <40184feb-4053-4ac3-8eaa-c3bd9cd8a77c@googlegroups.com> <10272577-945f-4682-85bc-8ad47f3653ae@googlegroups.com> <87si8i81k2.fsf@atmarama.net> <8076cbd0-2655-4c98-b70e-cb5f0c32e4ba@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="4fa08f1ce1db3b0ae8c51611453a050c"; logging-data="30400"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6CEs7envrffOjvHxGpQBT" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:tLuJzA9/fm+7Jdmyhiq3rmWlzH4= sha1:ZqeyHuCeRAsZqqOTYfuiDVvIyQo= Xref: news.eternal-september.org comp.lang.ada:27069 Date: 2015-07-28T00:22:16-07:00 List-Id: Georg Bauhaus writes: > why would C, say, be better for prototyping than Ada? When would SETL, > or Python, or BigEEMathSimPack be better suited? See: Haskell vs. Ada vs. C++ vs. Awk vs. ...: An Experiment in Software Prototyping Productivity by Paul Hudak and Mark P. Jones http://web.cecs.pdx.edu/~apt/cs457_2005/hudak-jones.pdf > How is a prototype useful when the language used for prototyping > tends to vaporize the Why-and-How of its choices and structure?) It lets you test out the intended program features and solidify the specification. In fact you often don't start with much of a specification at all, but rather just a general idea of what you're trying to do. Then you try things out, squeeze things in, get feedback from users and iterate the design, etc. At the end you've got something you can use as a reference when figuring out what a more permanent version should do. It's like making a pencil sketch before starting an oil painting.