Deutsch English Français Italiano |
<vbaf4s$3vcq1$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Brett <ggtgp@yahoo.com> Newsgroups: comp.arch Subject: Re: Computer architects leaving Intel... Date: Wed, 4 Sep 2024 20:15:24 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: <vbaf4s$3vcq1$1@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> <vb85a3$3gq7e$2@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 04 Sep 2024 22:15:25 +0200 (CEST) Injection-Info: dont-email.me; posting-host="59148afa0b64ac6c8e93bd21d62f7adc"; logging-data="4174657"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX196ArwvMaMUyJfw4mBYuwfP" User-Agent: NewsTap/5.5 (iPad) Cancel-Lock: sha1:dCYge+7Ok4ODIIHW0YnQzIjKK6U= sha1:MjyiRBISxLQPIL35e+qkHZ5cYlM= Bytes: 2538 David Brown <david.brown@hesbynett.no> wrote: > 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. Wrong, the last version of Swift added all the garbage programming concepts that one should avoid. You have to give people the tools to do anything.