Deutsch English Français Italiano |
<vb85a3$3gq7e$2@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: David Brown <david.brown@hesbynett.no> Newsgroups: comp.arch Subject: Re: Computer architects leaving Intel... Date: Wed, 4 Sep 2024 01:15:14 +0200 Organization: A noiseless patient Spider Lines: 19 Message-ID: <vb85a3$3gq7e$2@dont-email.me> References: <2024Aug30.161204@mips.complang.tuwien.ac.at> <memo.20240830164247.19028y@jgd.cix.co.uk> <vasruo$id3b$1@dont-email.me> <2024Aug30.195831@mips.complang.tuwien.ac.at> <vat5ap$jthk$2@dont-email.me> <vaunhb$vckc$1@dont-email.me> <vautmu$vr5r$1@dont-email.me> <2024Aug31.170347@mips.complang.tuwien.ac.at> <vavpnh$13tj0$2@dont-email.me> <vb00c2$150ia$1@dont-email.me> <505954890d8461c1f4082b1beecd453c@www.novabbs.org> <vb0kh2$12ukk$1@dont-email.me> <vb3smg$1ta6s$1@dont-email.me> <vb4q5o$12ukk$3@dont-email.me> <vb6a16$38aj5$1@dont-email.me> <jwv8qw8o7zg.fsf-monnier+comp.arch@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 04 Sep 2024 01:15:15 +0200 (CEST) Injection-Info: dont-email.me; posting-host="007bf4bb57fea4fb73ad9dc6d5dccf66"; logging-data="3696878"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+J+XbCKeJOrLIC40AROzAZWiNJXyE1UcU=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:3W0gHO1EQULX7jhgycfoffMX6jg= Content-Language: en-GB In-Reply-To: <jwv8qw8o7zg.fsf-monnier+comp.arch@gnu.org> Bytes: 2315 On 03/09/2024 21:28, Stefan Monnier wrote: >> My impression - based on hearsay for Rust as I have no experience - is that >> the key point of Rust is memory "safety". I use scare-quotes here, since it >> is simply about correct use of dynamic memory and buffers. >> >> It is entirely possible to have correct use of memory in C, > > If you look at the evolution of programming languages, "higher-level" > doesn't mean "you can do more stuff". On the contrary, making > a language "higher-level" means deciding what it is we want to make > harder or even impossible. > Agreed. I've heard it said that the power of a programming language comes not from what you can do with the language, but from what you cannot do.