From nobody Sun Sep 8 08:39:35 2024 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X1k0r0l3Tz5WNyd for ; Sun, 08 Sep 2024 08:39:40 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1k0q0mJNz4X7w for ; Sun, 8 Sep 2024 08:39:39 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=ZpMitlir; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::334 as permitted sender) smtp.mailfrom=paulf2718@gmail.com Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-42bbd16fcf2so29930435e9.2 for ; Sun, 08 Sep 2024 01:39:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725784777; x=1726389577; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=KXnsKNilK5hrzuOrcvhWYSf7cQiAGnPTx/ZGScuR50Q=; b=ZpMitlirDVRZmej2CcIeTdELmwC6LOz2jWc6sK07Bv51bhhWkVAky1y+mQmsAuYTmU y9+YWsighorfC/kUuIDLcfo5qz6Si46tR8sv1XM7tXX7lbmjIdMJgbgQu4mQ0N4rnir3 nCRXjNYViRlNfYmYmz81LX62wHvgrvb8LcJP/9XbiA9TfbgaLwzhafHlBgDNvxOicHQp g3rLTTs0pXKdxdpkpHC1jmOAnlOu3gBPjwK0Axm+MnKVBtk335YjIHScyaYo2S3tqN94 hNfxw02sV/0t0+CX74SPrKrVYlx1sWwZButhpkF4QPKBOpbud57+yzfFRX9g2L3K+7Bc vHIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725784777; x=1726389577; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KXnsKNilK5hrzuOrcvhWYSf7cQiAGnPTx/ZGScuR50Q=; b=b56t8qxu5IvQGkt/M9lowsLGzDPBWGopiUXsxVmEfWv7CjPrNjOZIb3sCtKs4ulzL+ olEugMxcNixxOCJrp+mEZ0jqDF5Mfb6Ls1UMja+ZPZ/lo4FTL59IpouKoIWEEyh6ttRO tr2D1E6/qUQi/3PA8TpI0BAasooam/TZTiw7oXJOyObcupEnLgubyWuEh6qSioUzp6/8 3Ifir2VW42GlX2O21XVgge5aqe5RYta6BBohSDIMDV27mwtWssvQ+bYarQs+/5UcVFlV wlb3yXqEXoy5ir/nyi9tavaiQndDbQR+sV4f4GdVq+ZwF1K+vb6a2LeZO6M7OgaAJ7u3 aDSw== X-Gm-Message-State: AOJu0Yx89L/gI08GSKdjNM04Wod/liAjqNpcp4KgNoU9PL74O85ESFDw z5BDVYGXaglkrfHdyTxHhIgNha2NlzPAkcXoz3/3o+42v34QEUeWdKkMXg== X-Google-Smtp-Source: AGHT+IE0WEBhARvAcxdSb1v3xdHdTvmtDdRr3E1cxpBX/jQDRAaadRODuh1DDWPUo/saX/L/i19q8g== X-Received: by 2002:adf:fc0a:0:b0:374:c8dd:ea47 with SMTP id ffacd0b85a97d-37894a5ff7emr2491104f8f.50.1725784776557; Sun, 08 Sep 2024 01:39:36 -0700 (PDT) Received: from ?IPV6:2a01:cb15:801f:7500:1aa9:5ff:fe16:2efb? ([2a01:cb15:801f:7500:1aa9:5ff:fe16:2efb]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-42cb099acf6sm33308695e9.9.2024.09.08.01.39.36 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 08 Sep 2024 01:39:36 -0700 (PDT) Message-ID: <9adc3619-bc38-4fe7-bf16-20e0dfb3b619@gmail.com> Date: Sun, 8 Sep 2024 08:39:35 +0000 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: The Case for Rust (in any system) To: freebsd-hackers@freebsd.org References: <20240905194529.3szOViVM@steffen%sdaoden.eu> Content-Language: en-US From: Paul Floyd In-Reply-To: <20240905194529.3szOViVM@steffen%sdaoden.eu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::334:from] X-Rspamd-Queue-Id: 4X1k0q0mJNz4X7w On 05-09-24 19:45, Steffen Nurpmeso wrote: > Alan Somers wrote in > |The real takeaway here is that C is no longer sufficient for writing > |high quality code in the 2020s. Everyone needs to adapt their tools. > > I *totally* speak against this. > Quite the opposite i claim that C was safe already fifty years Is that a joke? Do you have any evidence? It sounds like wishful thinking to me. When I explain to my young colleagues that learnt to code in Java and Rust how K&R C function definitions "worked", their eyes open wide in amazement. > ago, it is just that the occasional one does not realize it. > *Nothing* prevents you from using a string object instead of > direct memory accesses, a vector object instead of arrays managed > via realloc(), and all that. *Nothing > If *you* do not do that that is your fault and you are a bad > programmer; moreover, you should not be allowed to vote in > a democratic environment (surely you do not read all the > magazines and newspapers, and watch or hear to policital > emissions, in order to build yourself a *real* opinion), be > enabled to drive a car, and what else not. I'm not sure that I follow your argument. Are you saying that you can build memory safety into C code and that if someone doesn't so they are a bad programmer? What's the point - why not just use a memory safe language? A+ Paul