Why do people learn C and Operating Systems in 2026 when Rust exists and #[no_std] is a thing?
>>109165032because they're a perfect programmer who would never make any trivial memory mistakes.
>>109165032this might be a surprise to you, but most existent software is still written in c and someone might want to modify it without a full rewrite.
why does rust mean you shouldn't learn operating systems wut
>>109165032to appreciate driving automatic, you must experience driving stick.to appreciate driving stick, you must experience driving automatic.rust gives you both, but C gives you a more authentic 70's era stick experience.
>>109165191This. I think it's literally one guy here (possibly a tranny) who does all the shilling. He would also derail unrelated threads and try and make them about Rust. Probably doesn't even program Rust or if he does, his code is awful.
>>109165032Horrible language for horrible people.
>>109165032because Rust's primary selling point--memory safety--comes with a whole lot of asterisks behind it, and any low-level Rust is going to involve a lot of unsafe codebecause Rust is still evolving, but C99, a common standard C programmers program against, has been fixed for decadesbecause every operating system currently in wide use is written at least partially in C, and systems programming for them, even in Rust, is going to involve interacting with Cbecause you can get a lot done with C and ~1MiB of libraries, but the Rust equivalent usually involves downloading gigs of cargo dependenciesbecause Rust has glacial compiles compared to Cthose are a few reasons, there are dozens of othersi'm actually translating a program i wrote in C to Rust, but it's mostly a learning exercise and a kind of experiment to see if i can do it with just the Rust stdlib (the C program has no external deps outside of libc)
for the uninitiated: this is a filler seethe thread before (((they))) create some sort of negative narrative around RCN, and publish it via their (((e-celebs))). The zio entity is asleep right now. So expect a delay of a few hours before an (((e-celeb))) spam thread of a just published (((e-celeb))) video shows up.Thank you for your understanding. And...Thank you for your attention to this matter.https://rustfoundation.org/rust-commercial-network/
>>109165373what asterisks does memory-safe rust come with? safe rust is always safe to my knowledge, but the rest of your points are perfectly valid.>>109165462yes jews created rust to live rent-free in your schizo brain. there's always a higher power orchestrating everything and not just people developing superior software.
>>109165032I spun up a little cloud machine once and wanted to test rust. I wrote a console hello world program. It didn’t compile. The rust compiler needed more than 512MB of RAM (smallest on digital ocean at the time) in order to compile.I never touched rust again. It’s just more bloatslop.
>>109165032Not everyone is willing to transition.
>>109165032Cause we're not gay.
>>109165032Every cool bugs in games were made in C, you can't replicate those things in with OOP.
>>109165537>yes jews created rust to live rent-free in your schizo brain.you read my comment in reverse, amigo.
>>109165537>what asterisks does memory-safe rust come with? safe rust is always safe to my knowledgeunless the compiler and stdlib are formally verified to prove that their memory safety guarantees hold before every release, it's not possible to say "safe Rust is safe," only "we think safe Rust is safe"then there's the fact that non-trivial, low-level, performant Rust code will always use unsafe; the vast majority of Rust code currently in production either uses unsafe code itself, or depends on crates that, themselves, use unsafe codethe typical Rust cope is "oh, well it's all safe except for this little bit of code over here, and we thought real hard about that and we're pretty sure it's safe"of course, C and C++ programmers have been shipping code for decades that they were "pretty sure" was safe
