From nobody Sun Jan 21 07:32:58 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 4THlTr6HFhz56qYV for ; Sun, 21 Jan 2024 07:34:08 +0000 (UTC) (envelope-from lain@fair.moe) Received: from mail.076.ne.jp (mail.076.ne.jp [45.76.218.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4THlTn6dlNz4rjQ for ; Sun, 21 Jan 2024 07:34:05 +0000 (UTC) (envelope-from lain@fair.moe) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=076.ne.jp header.s=dkim header.b=KkYvlkMp; dmarc=none; spf=none (mx1.freebsd.org: domain of lain@fair.moe has no SPF policy when checking 45.76.218.69) smtp.mailfrom=lain@fair.moe Received: from mail.076.ne.jp (localhost [127.0.0.1]) by mail.076.ne.jp (Postfix) with ESMTP id 4THlTc72CQzW42R for ; Sun, 21 Jan 2024 16:33:56 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=076.ne.jp; h= user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:to:from:date; s= dkim; t=1705822435; x=1708414436; bh=QRASqGoGPLPOeE7+Ian7bmjtiWR 8o5yyyxGWNMYxnNg=; b=KkYvlkMpubMV/GjvpwOFONccdSTW4R4HuR6R1Iaz/CP VT+XGBvMVQTIzzOnpzQI2N4m5+R2N6SbTkXgV0Q6M+ZEgrVmKOEM1hFx5UWestxA POXqjB1FnacJnP7OrgQQb+32PNZxVWea7L5V5OdlBheM+TgSiW/hflup1tyvY+pC lFun4KkhdHKqtDOxdOF/wbu3BR0/d8Kxh9IqG91H55Ke02Q11eWsHb/ali5jkukw 0o97sYALXaZPPnSfUrTFCD+IAg5zukwkDgKHkWXUCNGCbRvDqsQ/s02YA6IeEfEf PPbjxDSPc3pdbDLNn74t+t2TDfy5dHmDB23vIDYjiCg== X-Virus-Scanned: Debian amavisd-new at guest.guest Received: from mail.076.ne.jp ([127.0.0.1]) by mail.076.ne.jp (mail.076.ne.jp [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nySd7lXfowtF for ; Sun, 21 Jan 2024 16:33:55 +0900 (JST) Received: from mail.fair.moe (ip1.193.076.moe [219.117.254.193]) by mail.076.ne.jp (Postfix) with ESMTPSA id 4THlTb6tqPzW3wr for ; Sun, 21 Jan 2024 16:33:55 +0900 (JST) Date: Sun, 21 Jan 2024 16:32:58 +0900 From: "lain." To: freebsd-hackers@freebsd.org Subject: Re: Re: The Case for Rust (in the base system) Message-ID: <5as7lcxskqe6rug25i6jlwtinfg5hrt2kbeo3t3lp5on33fkbv@opjtc4eyztl3> X-Location: =?utf-8?B?IkVhcnRoL+WcsOeQgyI=?= X-Operating-System: "GNU/Linux" References: <1673801705774097@mail.yandex.ru> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bnx6yanxghufx6kl" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20231221 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.90 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[076.ne.jp:s=dkim]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[fair.moe]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:20473, ipnet:45.76.192.0/19, country:US]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[076.ne.jp:+] X-Rspamd-Queue-Id: 4THlTn6dlNz4rjQ --bnx6yanxghufx6kl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable So just like Linux, FreeBSD is going to put the Rust compiler into the system? Just to put my own perspective into the mix, the same opinion I had for Linux, and so many other projects: why Rust? Just like Java and Microsoft Java (and by that I mean C#) in the 2000s, Javascript and Python in the 2010s, and C++ in the 1990s, it looks like Rust is the new fad language in the 2020s that will become irrelevent somewhere in the 2030s, and there will be calls to rewrite legacy Rust programs to whatever is the hip language in the 2030s until that goes out of fashion by the 2040s. My bet on what the 2030s hip language will be is probably Zig, and 2040s would be Jai or Carbon, considering the pattern so far. One argument I see a lot is to make stuff ready for the next generations of programmers to take over as the older programmers retire, but as a younger C developer, I can't see how C is harder than the language of the decade. On the contrary, I find it a lot easier to code in C, because as long as you keep it simple (the hardest part for most programmers), all you need is a text editor and a compiler, and you learn a lot about the hardware you're working with along the way. With Rust, the compiler stops you from destroying the memory, but will never teach you how you can avoid that, simply because there's no incentive in learning that. In the short term this might be beneficial, but in the long term this can be catastrophic, as the amount of people who understand hardware declines, so does innovation, productivity, and even the ability to maintain already existing software. Of course FreeBSD is not my project, and the FreeBSD devs ultimately decide its direction, but nobody has historically listened to me until it was already way too late. I just wanted to provide my input on the whole "rewrite programs that work perfectly fine in Rust" mentality that has spun up in recent years, which already affected compile times spectacularly in bad ways. --=20 lain. Did you know that? 90% of all emails sent on a daily basis are being sent in plain text, and i= t's super easy to intercept emails as they flow over the internet? Never send passwords, tokens, personal information, or other volunerable in= formation without proper PGP encryption! If you're writing your emails unencrypted, please consider sending PGP encr= ypted emails for security reasons. You can find my PGP public key at: https://fair.moe/lain.asc Every good email client is able to send encrypted emails. If yours can't, then you should consider switching to a secure email client= , because yours just sucks. My recommendations are Claws Mail or NeoMutt. For instructions on how to encrypt your emails: https://unixsheikh.com/tutorials/gnupg-tutorial.html --bnx6yanxghufx6kl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEEozVhUpXECiNYIKIXtWNzC1Y29b0FAmWsyKcACgkQtWNzC1Y2 9b20ewwAk4db0OrhHF238OkwrqRkpc9CiRDKnHpjNYfp78HqJlmctjcPXn7+QFLL 0mE1C2BkLLxm1TJhiBB1Lti9b1RDgJhNOoiKyE10X2rD2e798Hftnt9IzeKMI0oL J0iDwYQVDqHOFVJIZ6moDrBbHauDErJ6+OoVPXO5k1reLHqwNcMBxSbAgDqmhI5l D+wv6zpaRpzW5W8XqtjOhYp9cJo6UUJyoMd8yCWxwog95BkTcPao9ppV/5yhSUXi dvzzblx/V60sq00bmtauVdw/j4VAJ1H5L3KAXe26rJAhCmlwGIpfaBcaUDb7brH3 UYyUe0NdbvoKN03StLs6Cs0uBy21u9mVArcPicWrEOHhnEPXmWQJLkInXVbVX0JD zv+G/tVhznSSi69m9ClppWapgRzt2NdHCmM/11YAPek958Ypi2yWvb/LQ319enX7 Evr3Ctg1UIV6rrsymv2RjMWsI1/vP0FfgD6qpaFmz5145pc3jeJ/0vqrme28Huiy hiIHatYL =JEl9 -----END PGP SIGNATURE----- --bnx6yanxghufx6kl--