Date: Tue, 03 Sep 2024 10:57:12 +0000 From: fvalasiad <fvalasiad@proton.me> To: "lain." <lain@fair.moe> Cc: freebsd-hackers@freebsd.org Subject: Re: The Case for Rust (in the base system) Message-ID: <dHVxEgS5MbvPceHSJF-G42LSk22NXsjKKwPzFagCTDNsKO4zgQpZKjteuGEAdO2ikPVIkP-3x6r2I1caTlM2YQrH3vjrWzgtRUVFtwsObOA=@proton.me> In-Reply-To: <jbuwu5qby7gb7abym3msutmojx26qhwcgyyb2cb6nfnf2w4a6h@otor5sawmss5> References: <CAOtMX2hAUiWdGPtpaCJLPZB%2Bj2yzNw5DSjUmkwTi%2B%2BmyemehCA@mail.gmail.com> <vdmg5zocd6wqcwc2bvzvzqn4bii2pwdc2r4mgnisukfkboj6nf@f7lv5quu4fjx> <CAOtMX2iDK3uN_oQgzzZAdoOZCfNsnvpefeZvKoTCRmPBhZywzA@mail.gmail.com> <CANCZdfqB1%2B-8BkpKwKoCM%2BzM4mCOFy63yHr1Pco7MnT1DFkb4w@mail.gmail.com> <knnsh327gxyvaajwrymvflnivf3tsnigyqw2d6etfhb4irft3x@ydkh3zmb6uch> <CANCZdfoHjYUDeNo78qk6BjHfRgwgDbuuVjD5D9uG6tyCk81-ew@mail.gmail.com> <Zq69w1D7aYRiNdPx@kib.kiev.ua> <CAFYkXjmURZwBbrFL=uWT%2BDZ6h_qjjpoucxW4-3CpDhKn3XX2gg@mail.gmail.com> <jbuwu5qby7gb7abym3msutmojx26qhwcgyyb2cb6nfnf2w4a6h@otor5sawmss5>
next in thread | previous in thread | raw e-mail | index | archive | help
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. <lain@fair.moe> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dHVxEgS5MbvPceHSJF-G42LSk22NXsjKKwPzFagCTDNsKO4zgQpZKjteuGEAdO2ikPVIkP-3x6r2I1caTlM2YQrH3vjrWzgtRUVFtwsObOA=>