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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Received: by 2002:a6b:ef12:: with SMTP id
 k18-v6mr3976305ioh.31.1531560454013;
        Sat, 14 Jul 2018 02:27:34 -0700 (PDT)
X-Received: by 2002:aca:f495:: with SMTP id
 s143-v6mr1881215oih.7.1531560453843;
 Sat, 14 Jul 2018 02:27:33 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!g2-v6no3319021itf.0!news-out.google.com!n194-v6ni2477itg.0!nntp.google.com!g2-v6no3319020itf.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 14 Jul 2018 02:27:33 -0700 (PDT)
In-Reply-To: <bf8f8498-f017-47dd-bf1f-188c7ceb5b28@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=92.186.158.92;
 posting-account=xd0OrwoAAABQUGXxWZdZWv6VwPFSqa1J
NNTP-Posting-Host: 92.186.158.92
References: <1c73f159-eae4-4ae7-a348-03964b007197@googlegroups.com>
 <878t9nemrl.fsf@nightsong.com>
 <d64089d4-af9d-43d9-b72b-a73d3fff1f00@googlegroups.com>
 <bf8f8498-f017-47dd-bf1f-188c7ceb5b28@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <62df3c25-057c-4cc5-a899-b91413613b83@googlegroups.com>
Subject: 
 =?UTF-8?B?UmU6IEhvdyB0byBnZXQgQWRhIHRvIOKAnGNyb3NzIHRoZSBjaGFzbeKAnT8=?=
From: jm.tarrasa@gmail.com
Injection-Date: Sat, 14 Jul 2018 09:27:33 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:53796
Date: 2018-07-14T02:27:33-07:00
List-Id: <comp.lang.ada>

> > 4.  It is not hindered by backwards compatibility concerns.  They take
>=20
> There are a lot of people who would love to see a new Ada version break a=
way from the previous versions, possibly even a rewrite removing all the cr=
ap that's not really required and basically, an Ada for the 21st century.

Backward compatibility is great. Most software that ran in Windows 95 still=
 runs in Windows 10. On the other side, Gtk: Themes written for 3.18 break =
in 3.20 https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/

But there is a point that you must correct problems even breaking compatibi=
lity.  I know that in software, with long term deployments, it is not easy.=
 Many backend software in banks and assurance companies is still COBOL, and=
 they don't dare to migrate it. But someday, you have to break with past to=
 advance.

It would be wonderful that Ada experts that have experience to know the pro=
blems and drawbacks of Ada, correct them even breaking compatibility.
That would be the "Ada Successor Language"
https://groups.google.com/d/topic/comp.lang.ada/CrPqENqxl4g/discussion
No chance. It looks like current specification is perfect so far, only need=
s additions, not amendments.
Ada experts don't want to change anything, and non Ada experts create Go, R=
ust, Swift, Erlang, Nim...