From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-91-241.ec2.internal X-Spam-Level: X-Spam-Status: No, score=0.9 required=3.0 tests=NICE_REPLY_A, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.6 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "G.B." Newsgroups: comp.lang.ada Subject: Re: US Government looking into memory safe programming Date: Mon, 25 Sep 2023 17:55:08 +0200 Organization: A noiseless patient Spider Message-ID: References: Reply-To: nonlegitur@notmyhomepage.de MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 25 Sep 2023 15:55:09 -0000 (UTC) Injection-Info: dont-email.me; posting-host="efa4bbc0a23c704aa7def0056e5acaed"; logging-data="2106295"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/oUSaO+6C8y29HXSdgpz2dpCXUMfD2AzA=" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Cancel-Lock: sha1:UA6Mk8Fut7j4QCmpaR5Pwfnj63E= Content-Language: en-US In-Reply-To: Xref: news.eternal-september.org comp.lang.ada:65721 List-Id: On 25.09.23 12:38, J-P. Rosen wrote: > Le 25/09/2023 à 11:59, Stéphane Rivière a écrit : >>> How long before they relax the requirements >>> and idiots say "we can use C again, yay!"? >> By the time they discover Rust ? > > Or when they realize that there is only one rust compiler, and therefore that a single compiler virus could ruin the whole defense system. > Maybe, given the emphasis on tools, verification and best practices, they might consider sub-languages, or profiles, of several existing languages. It's not like memory-safety cannot be made available in languages other than Rust, I should think? Though, it seems to me that Rust has so much better market-aware development strategies than any other language since C, outside Microsoft's or Apple's areas of sales. Also, I understand that Linux kernel development is steered towards Rust and LLVM. So, they have decided not to go back to the 80s, just pick some good bits and move on, possibly producing grust or crust while at it. In order to pick well from Ada and the concepts embodied in it, imagine what parts of Ada should be thrown out, ignoring commercial enterprises living off legacy business? What changes to Ada are a good fit while aiming at memory safety, verification support, or light weight and safe parallel execution? As you can see in [1], there is a suggestion to make money available to refactoring efforts. [1]: https://www.federalregister.gov/d/2023-17239/p-37