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!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.ada
Subject: Re: How to get Ada to ?cross the chasm??
Date: Sat, 28 Apr 2018 22:22:41 -0700
Organization: A noiseless patient Spider
Message-ID: <87wowqpowu.fsf@nightsong.com>
References: <1c73f159-eae4-4ae7-a348-03964b007197@googlegroups.com>
	<dbcb51b9-8ab9-4d39-bb70-47fdb15ebfd8@googlegroups.com>
	<pb7eii$bf1$1@dont-email.me>
	<b75ad71f-a917-4638-9b38-ccfe69b04e53@googlegroups.com>
	<slrnpdpiv9.ntv.address@is.invalid>
	<pbr3mi$leu$1@franka.jacob-sparre.dk> <87k1su7nag.fsf@nightsong.com>
	<pbtlno$3k2$1@franka.jacob-sparre.dk> <87po2la2qt.fsf@nightsong.com>
	<87in8buttb.fsf@jacob-sparre.dk>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org;
 posting-host="2973c66b8467d5e5c38d149f2cdfa94b";
	logging-data="30190"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/hGbRjgVKJDEDj6uTM6bqJ"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Cancel-Lock: sha1:kdSztlEoM3HSenb84juHpi4sDdk=
	sha1:vm5lJcHzcpeW5RwBreVd2Dd7puI=
Xref: reader02.eternal-september.org comp.lang.ada:51771
Date: 2018-04-28T22:22:41-07:00
List-Id: <comp.lang.ada>

Jacob Sparre Andersen <jacob@jacob-sparre.dk> writes:
>> I couldn't imagine writing a substantial server app entirely in Ada.
> Why not?  (That's what I spend most of my time doing.)  One of the two
> projects I'm working on now is already ~1M lines of Ada in the server.

Why write 1M lines of Ada when you can write 1/10th as much code in a
HLL?  Why worry about potential integer overflow every time you do
arithmetic?  How much of your effort goes into manual memory management?
Why not use a language and runtime that handles all that for you
automatically?

And if your app runs on one cpu, what does Ada's solidity get you under
Joe Armstrong (designer of Erlang)'s dictum that a non-distributed
system can never be reliable, since the power cord is a single point of
failure?  Conversely, if your app is distributed, what does Ada get you
that normal failover machinery doesn't?

> The other one...  The R and Python parts will be carefully shielded
> from the users and the internet by the Ada part.

That sounds like a much more practical approach.