h=uv7SYOUbaLWPfkiWsRJ5PmTqKcGIYs0LxzvKGHUARfE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=CHOkj3yGVvbp6h0UubbksrQwJv1uDAzRUaJdbul4tJLwtQe8fGYB1PciAwPfQUGiP 3FBlBxDn1QsG0UbAC9YKa9Fb7Eq2nuGGt8PSKDAORQQVOrMmcZ6OyQXzsaq+xon3Hg hM565EJLPI01Xi7LioTa44lSiLzxKlfxtcCWCwLc3p+AlyIx3eQM3T530bMRQj+TAu 2qPokYnG2oVarHHV5zYLqt67/YZqdjuwHW4C0g91wdr8HktPwJRP93BrGFwbMlH/FR Zzc8dfkMAGtZid3tvTDkcyt/A+49jlTf2Cz6ZT/GUHLEH21VSQtXHfMk7E/g6rAV7S ovEPZxytM+9PA== Date: Tue, 03 Sep 2024 10:57:12 +0000 To: "lain." From: fvalasiad Cc: freebsd-hackers@freebsd.org Subject: Re: The Case for Rust (in the base system) Message-ID: In-Reply-To: References: Feedback-ID: 78761413:user:proton X-Pm-Message-ID: ebaed0d8b2e6c3b451343fa9b974cf0aba80a004 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: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH] X-Rspamd-Queue-Id: 4WyjHy5c5Jz4J7l This is rather pessimistic though, just because a kernel was initially writ= ten in C, means that it won't ever have a chance at another language? I am pulling this out of my *** but C devs seem to be in decline, what's wo= rse, having no devs or having devs that specialize in other languages? Still weird that rust was added to a kernel before C++ though, C++ being al= most a superset of C would have probably helped with its adoption. But people still (also) refer to C++ when they wanna talk about memory bugs= , as if that problem hasn't been solved by RAII for a decade+. Yes, in legacy codebases that used C++ as "C with classes" per its original= name, memory bugs are still found today, but I'd be really interested to s= ee statistics and comparisons on the matter when compared to a modern C++ c= odebase. Again, rust community being more vocal gives the false idea of a thriving d= eveloper community but in reality rust is hard to use and I struggle believ= ing people would choose rust to contribute to FOSS kernels if they find dev= eloping in C and C++ difficult. Source: I made it all up, very happy to see myself proven wrong in the futu= re. Can't deny that I am eager to see where this whole situation is going i= n the times to come. Fotis On Tuesday, September 3rd, 2024 at 10:29 AM, lain. wrote: > On 2024=E5=B9=B409=E6=9C=8803=E6=97=A5 00:23, the silly Tomek CEDRO claim= ed to have said: >=20 > > Rust for Linux maintainer steps down in frustration with 'nontechnical > > nonsense'. > >=20 > > Community seems to C Rust more as a burden than a benefit > >=20 > > https://www.theregister.com/2024/09/02/rust_for_linux_maintainer_steps_= down/ > >=20 > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >=20 >=20 > Exactly as I predicted. > Only a matter of time until a massive hype settles, and a sense of > reality returns again. >=20 > Rust works on Redox, because that OS has been written in Rust from the > get go. > Rust does not work on Linux or FreeBSD, because those are written in C. > It's really that simple! >=20 > "But Unix was written in Assembly, and got rewritten in C!" > Yes, but C is pretty close to Assembly, and the Unix codebase back then > was still small, so a rewrite was pretty easy. > Good luck rewriting the entire Linux kernel to Rust without committing > suicide though. >=20 > -- > lain. > PGP public key: https://fair.moe/lain.asc