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: Ada Successor Language
Date: Wed, 13 Jun 2018 22:17:37 -0700
Organization: A noiseless patient Spider
Message-ID: <87y3fi6j66.fsf@nightsong.com>
References: <5e86db65-84b9-4b5b-9aea-427a658b5ae7@googlegroups.com>
	<878t7u1cfm.fsf@nightsong.com> <fnpmtjF19kpU1@mid.individual.net>
	<8a65f8ff-4a75-43f2-884c-6872780f7ea8@googlegroups.com>
	<771e8e35-b71a-499d-a0fe-bb0df1de22ab@googlegroups.com>
	<c65805c1-2b6b-431e-aabf-f9ae64625f2a@googlegroups.com>
	<92741619.550509671.540055.laguest-archeia.com@nntp.aioe.org>
	<81e22064-bb0e-4e0b-982a-c17a2cad5977@googlegroups.com>
	<ly4li7kwbm.fsf@pushface.org>
	<1b03e4ff-daf1-4c13-84ef-13aec1ba96e9@googlegroups.com>
	<87po0upevs.fsf@nightsong.com>
	<ea4260e4-5ab9-45fb-a35f-3a3e4dd48c6d@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org;
 posting-host="4b1c06a3b2db4f78fc98527db2f34c17";
	logging-data="17450"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18N0hOtO/3FRYVL9GNPodH7"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Cancel-Lock: sha1:Ff7qBouLiHb/oGcFuWYsYdHMLck=
	sha1:Bsl8QtXYtAApVRyELKxzSQDe2vw=
Xref: reader02.eternal-september.org comp.lang.ada:53092
Date: 2018-06-13T22:17:37-07:00
List-Id: <comp.lang.ada>

Shark8 <onewingedshark@gmail.com> writes:
>> Fancy CI that I've seen
> Relatively new; when they should have been industry standard two
> decades ago?

No I don't think the associated technology or the machine resources were
available that easily 20 years ago.  

> The FS is NOT a good substitute for a DB,

Depends on wat you are doing

> (e.g. case sensitivity, the path, the path separator, timestamp
> resolution, etc.)

Might not matter, depending on what you are doing.

> Except you're ignoring things like the Rational 1000 which was

Whatever that is, almost nobody uses it now, probably for a reason.

> This is the whole reason that JSON is popular; because it "solves" the
> problem of text-stream consistency...

JSON is just restricted, curly-braced S-expressions.

> sadly, the industry fails to realized that these serialize/deserialize
> problems were already solved via ASN.1.

That's just another thing to parse and unparse.  Here's my favorite
ASN.1 related rant:

https://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt

That said, reprocessing ad hoc text formats was more tractable in the
20th century Unix era, when there weren't so many programs around.  This
stuff exists in the real world after all.

> I highly recommend you watch this video:
> http://www.youtube.com/watch?v=8pTEmbeENF4

On my list.