Deutsch English Français Italiano |
<e869564c7aec3d40d2ac8b5aa003cef4@www.novabbs.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: mitchalsup@aol.com (MitchAlsup1) Newsgroups: comp.arch Subject: Re: Computer architects leaving Intel... Date: Wed, 4 Sep 2024 20:18:55 +0000 Organization: Rocksolid Light Message-ID: <e869564c7aec3d40d2ac8b5aa003cef4@www.novabbs.org> 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> <vbaf4s$3vcq1$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="867889"; mail-complaints-to="usenet@i2pn2.org"; posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A"; User-Agent: Rocksolid Light X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Site: $2y$10$p51oO79RHpAhb/OJI.NNAe5X.nO1qe/uefH6xUOQ2YNBf4cvXfvu2 X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8 Bytes: 2690 Lines: 30 On Wed, 4 Sep 2024 20:15:24 +0000, Brett wrote: > 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. It is impossible to create a computer programming language where the programmer cannot shoot himself in the foot.