Hal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agoMicrosoft wants to replace its entire C and C++ codebase, perhaps by 2030www.theregister.comexternal-linkmessage-square130fedilinkarrow-up1259arrow-down115cross-posted to: programming@programming.dev
arrow-up1244arrow-down1external-linkMicrosoft wants to replace its entire C and C++ codebase, perhaps by 2030www.theregister.comHal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agomessage-square130fedilinkcross-posted to: programming@programming.dev
minus-squareⓂ3️⃣3️⃣ 🌌@lemmy.ziplinkfedilinkEnglisharrow-up5arrow-down5·2 months agoThat’s funny because using unsafe might be an hint that Rust is not the right tool for the job. Yet we have rust in the kernel, rust coreutils… I just can’t wrap my head arout it, yet.
minus-squareboaratio@lemmy.worldlinkfedilinkEnglisharrow-up3arrow-down1·2 months agoYou shouldn’t have said that. Now the rust zealots are going to come for you.
minus-squareⓂ3️⃣3️⃣ 🌌@lemmy.ziplinkfedilinkEnglisharrow-up2arrow-down1·2 months agoGot downvoted, here they come…
minus-squarefilcuk@lemmy.ziplinkfedilinkEnglisharrow-up1·2 months agoUnsafe is expected and necessary in certain situations. Using other languages doesn’t change that fact. It’s talked about in the docs
That’s funny because using unsafe might be an hint that Rust is not the right tool for the job. Yet we have rust in the kernel, rust coreutils… I just can’t wrap my head arout it, yet.
You shouldn’t have said that. Now the rust zealots are going to come for you.
Got downvoted, here they come…
Unsafe is expected and necessary in certain situations. Using other languages doesn’t change that fact.
It’s talked about in the docs