>B-but muh C>B-but muh C++Both don't have await or async features.They are garbage.In the age of internet, you really need those things.>B-but muh wait(response) {}This is shit code and not clean at all.>B-but muh C#>B-but muh typescriptDoes not compile into computer language>B-but muh pythonThis is shit language for retards
I mostly agree though i would say C# is also a fine choice. It's one of the faster languages and though not as fast as rust the tradeoff is that you get simplicity, fast compile times and native hot reload support.
>>110203754Tranny thread>hide
>>110203815>>110203842Not an argument
>>110203754What does Rust give me that Ada doesn't?
>>110203754
>>110203875
>>110203875>>110203905this fag is more mentally ill than rustroons
>>110203978get memed faggot
>>110204005
>>110204005Captions on stock photos are so 2000 late, get with the times
>>110203754>Both don't have await or async features.https://en.cppreference.com/cpp/keyword/co_awaitThis doesn't change the fact that async programming in C++ is a nightmare.
>>110204045
>>110203754I like rust because I can just tell Claude to make things with it and it works every time. I’ll never actually read it myself though that’s for transvestites
>>110203863GRIDS and a discord server to groom children
>>110204078The image part of imageboards is definitely dead with the kind of shit you're trying to pull in current year
>>110203754>async featuresyou failed at pointing even one language feature.>>110204182what's up your butt, you stupid nigger?are we supposed to post in a specific, pre-approved, way?I know what's up your butt, though. you are one of those faggots who like rust, you can't counter the "programming on training wheels" jokeor "I don't have mommy's permission to manage memory manually" with the lamest way possible: your ways are old.guess what faggot.Rust is from the same era and the only traction it gets is because trannies are seething about people not using or liking rust.
>>110203804>GC garabageInto the trash it goes
>>110203863>AdaIt doesn't guarantee 100% safety unlike Rust
Rust + Claude Code = Match Made in Heaven
>>110203804Hasn't Beef solved C#, and simple and compiled Oop?
>>110203754Rust is unironically great, but I wish it had a standard library the size of Java's. C++ is only good if you're willing to take the time to build your own ecosystem. C# is pretty good and sits right in the sweet spot, only thing I don't like is Microjeet's retarded ass naming conventions
Rust is so cool.
>>110207634you WILL depend on serdeso what if every single rust program in existence depends on the whims of a random dev?we just don't have the troonpower to integrate it and maintain it as part of the standard librarydeal with it, chud
>>110205066Okay, and why should I use Rust over SPARK?
IQ test for anons ITT:Does Rust use Garbage Collection?
>>110207717Support for dynamic memory allocations for example.
>>110203754as a rustacean, you are why people fucking hate us. please stfu
>>110203754>#include <linux/async.h>>#include <aio.h>>#include <sys/wait.h>
>>110203849dont care. still using c, rusttranny
>>110207717There's no reason to use Rust over Spark unless you want to write a memory safe calculator program, memory safe Game of Life, or memory safe Tetris. If you're really feeling up to it, you can port a previously 500 LoC 24KB program to a 3500 LoC, 600MB program requiring 320 dependencies. Or just use Ada, C, Perl, and Tcl like a sane and well adjusted human being.
>>110203754add async/await to c with a transpiler https://github.com/loosestrife/c42 because the iso c committee wont do it until you do if first
>>110207885>dynamic memory allocationBasically banned in my codebase (work with stuff that can kill people)
>>110209852apples mistake in ^{} was not providing a way to manually allocate the space and everyones mistake in async libraries is not transpiling the functions the boring way everyone recognizes. they needed to be thinking in transpilers like https://github.com/loosestrife/c42
>>110209852You aren't using Rust, you likely work with stuff meant to kill and maim people.
>>110203754Fortran mogs it
>>110207885Not allowed to do that under the guidelines for projects we use SPARK on lol
>>110209852>>110210662>why should *I* use X rather than Y>here is reason>but at my work *we* have to use YAre you retarded or something? What's the point of this wueston then if you are going to move the goalpost to your job's requirements that are independent of whatever answer you get?
>>110209810>There's no reason to use Rust over Spark unless you want to write a memory safe calculator program, memory safe Game of Life, or memory safe Tetris.You can implement all of that in both of them.Where rust shines over spark is normal software development because it allows you to actually do the basic shit you'd expect from a programming language like eg allocate data on heap. If you want to write a normal userspace graphical program or video game or web service, Rust is going to be much more useful and productive than trying to use SPARK for it. There is a reason why barely no one uses SPARK to write such programs.
>>110205021async programming without gc is pain
>>110203754Rust is objectively unproductive, forcing you to constantly waste time strategizing around the borrow checker. That's why no one wants to use it. Seethe about it.
>>110210980>constantly waste time strategizing around the borrow checkergit gud
>>110210958Depends on how much async you use. Something like Embassy is such a huge improvement I can't believe someone would still want to use FreeRTOS given a choice.
>>110210985Sorry, but just like most people who have ever tried this shitlang, I've got better things to do.
>>110203754>https://x.com/rauchg/status/2116218022793036140sorry buddy, we've moved on from Rust. it's just not a good fit for the agentic age.but in a computer museum of some sorts it will be a pretty interesting curiosity for the next generation to see Rusts entry and exit from software engineering!
>>110210998Understandable. This is not an easy skill to learn.
>>110211005Neither is shifting your voice up a register trying to sound like a woman, but you're dedicated.
>>110203754>await or asyncUse case?
>>110211012Well, I had no idea. I never felt a need to sound like a woman, but I hope you well on your journey of self discovery.
>>110211076>hope*wish
>>110204049Don't worry, it's a nightmare in Rust too
>>110203804>Visual code
>>110211076>retarded mumbling
>>110211121>mumblingI'm sure you will figure the voice out eventually. Good luck!
>>110211187>>110211187>"no u" didn't land as intended the first time so the kiddie's just gonna loop itTell you what: if I ever need the meager guarantees Rust offers, I'll just write it in a ustable programming language and then ask a token guesser to translate it into Rust. The mindless machine has long mastered your "skills".
>>110211005>This is not an easy skill to learn.Lmao is this what Rusttroons actually believe? It's like Leftoid mouth breathers with a 'women's studies degree' thinking they're now highly educated ahahaha!
>>110211233>ask a token guesserI hope you will pass as a real programmer one day as well!>>110211343>>This is not an easy skill to learn.>is this what Rusttroons actually believe?No, I just didn't want the anon to feel bad about it.
>>110211046making your code hard to follow and borderline impossible to debug. also crazy fast if you get it right.
>>110211398>more generic mumblingOk. Be sure to keep investing your time in the one programming "skill" that's actually fully replaceable by mindless models. :^)
>>110211422Sure thing. Two more weeks!
>>110211455Your own ilk have been doing it for months now. Unlike general programming competence, your "skill" of tard wrangling babby's dumbed down version of a proof checker is obsoleted. Seethe about it.
>>110211479Good luck!
>>110211479>I'm angry and stupid. Use C.
>>110203754>no dynamic linking>no standard>unreasonably long compilation times, because the only compiler is unoptimized garbage>the compiler also doesn't do real optimizations, praying the llvm compiler does its job for him>half-baked "functional programming">illusion of safety that shits itself at higher order functionsYeah, no thanks.
>>110211763>>no dynamic linkingWrong.
>>110211765Oh, has is been implemented already?
>>110211771It was available since the very start. You have no idea what you are talking about.
>>110211763>cjeet must shill against anything that threatens c
>>110211793>you can dynamically link stuff with extern "c" hackeryDon't tell me the language doesn't need a better way to do this.>>110211815If anything is getting replaced by rust it's C++. Any usecase in which rust would replace C is already mostly done with C++.
>>110211906>get proven wrong>time to move the goalpost
>>110211948Tell me how many people actually link their crates dynamically instead of having binaries the size of my porn folder.I just never get to see it as an end user of the software.
>>110211641>I'm losing my mind with rage and talking to the voicesDoesn't change the fact that your trivial niche "skill" has been obsoleted.
>>110211992
>>110212007>I'm losing my mind with rage and talking to the voicesThat's clearly you, cschizo. Take your meds.
>>110212010>rusttroons have no response so xey reply with meme catchphrasesevery time
>>110212029>n-n-no uTerminally retarded.
>>110212074It clearly is you. You're very mad and stupid.
>>110212091>NO U!!! NO U!!!Lol.
>>110212097Red herring fallacy. What you posted has nothing to do with anything. I called you mad and stupid. I didn't reflect any of your projections back in my last post.
>>110212119>I'm losing my mind with rage and talking to the voices about imaginary reddit fallaciesDoesn't change the fact that your trivial niche "skill" has been obsoleted.
>>110212129>I'm losing my mind with rage and talking to the voices about imaginary reddit fallaciesHope everything will turn out fine for you. Cheers!
>>110212129>Doesn't change the fact that your trivial niche "skill" has been obsoleted.can confirm. i was hired to rewrite some tools in rust due to security considerations and last week i got fired because one of the retarded aibros figured they can just use claude to do the job. i asked my manager who else is getting replaced and fired and he said it's only me because i'm the only one working as a human compiler and not actually doing any conceptual problem solving
>>110212214It's ok, anon. You can always learn a useful programming language, assuming you have any experience with programming beyond fizzbuzz and rewriting existing software in Rust.
>>110212226>assuming you have any experience with programming beyond fizzbuzz and rewriting existing software in Rust.i don't and not many people in the community do. it's literally over. thinking that all the "useful" code i ever wrote was just to train my own replacement makes me wanna kill myself
I knew a Rust dev who made $80 an hour just writing Rust and he was allowed to use LLMs too. I wonder how the schizo will react to this.
>>110212690this is cope, many people in the rust community are struggling and we're tired of malicious shills like you gaslighting us about jobs that don't exist
>>110212806This is NOT a Rust specific issue, you falseflagging cnile. Most C "programmers" don't have jobs, either. At least I know I'm contributing something to the computing ecosystem and the open source community meanwhile all you do is produce more buffer overflows
>>110212833>At least I know I'm contributing something to the computing ecosystem and the open source community meanwhile all you do is produce more buffer overflowsThis. Rust is a language for forward-thinking people and anticipates the end of capitalism. Imagine wanting the future of software to remain in the hands of wagies and the corporations that own them
>>110203754Can't you just use threads for that in C++? Or is there some difference that I'm not aware of?
>>110213209You can, he's just baiting syntax wars. Also std::async exists.
>>110213209OP is retarded. C++ has async/await.Also async/await is not the same thing as threads. There is some overlap in functionality but they are fundamentally different.Threads rely on OS for scheduling and context switching. They are kind of like separate processes and come with bigger overhead but simpler design and come with parallelism and preemptive scheduling for free.Async/await uses async runtime embedded in the application for scheduling. They are lightweight, faster and do not rely on any OS feature(so you can use them on bare metal, eg in embedded programming). However parallelism and preemptiveness depends on runtime you use, and your code can get arguably more complex.However given how many complains I've seen about C++ async implementation and seeing how no one uses it for low level programming, it's implementation is probably lacking. Still, in principle you can use both with both languages and both approaches have their benefits and drawbacks.
>>110210322>you likely work with stuff meant to kill and maim peopleGuilty as charged
Everyone I know who uses Rust is rich and looks like a mad scientist. Never seen a single Rust tranny.
>>110203754Rust would be fine if crates didnt exist and gccrs actually worked
>>110212214>>110212241>>110212833>>110212850Holy shit, I never realized Rust users were this pathetic...
>>110214471>jeet calling Rustwhites patheticHypocrite.
>>110214570>seething jobless commies>"white"
another unemployed troon thread
>>110214580>ur no longer ur race if jeet takes ur jobWow, the chutzpah. You're a very jewish jeet.
>>110203754I don't give a fuck about using the best language, I'll use the one that get me employed doign what I like which are still and C and C++.they're just tools bro, not a personality trait
>>110214634>C>employedLiar.
>>110214646I'm a 32yo straight caucasian male writting kernel-space shit and firmware in C and userspace software in C++life is good
>>110214730>life with C is goodLiar.
>>110214866linux dev is peaceful
>>110214886as a rust bro, ignore the rustard. linux dev is where its at
>>110214886Rust is in the Linux kernel.
>>110203754I love Rust as much as the next guy, but async/await is only really useful in web servers. They're totally fucking useless in systems and embedded programming. Also, C# does support native AOT compilation. You're kinda wrong on that one.
Rust is good because you can't do this.
>>110203754i never understood why rust is so webdev coded
>>110215812A fast backend is desirable and C is hell.
>>110215800It's undefined behavior (just as the C snippet you showed is also UB), but it *is* possible.static a: i32 = 42;static b: i32 = 27;fn main() { let p: *const i32 = &b; println!("{}", unsafe { *(p.add(1)) });}
static a: i32 = 42;static b: i32 = 27;fn main() { let p: *const i32 = &b; println!("{}", unsafe { *(p.add(1)) });}
>>110215848The only difference is the unsafe block. Rust completely supplants C even at ub.
>specification status: nonexistenthttps://github.com/rust-lang/specI will not consider Rust for even a moment until the spec is published.
>>110215860We can think of unsafe as an acronymUndefinedNonsenseSemanticsAllowedForExecution
>>110203754I didn't ask. I will continue using c# and you will continue seething, coping shidding and malding, bro.
>>110211046Anything that access some web service that needs to wait for the reply.
>>110203754C++ has co_await and shit, but it's basically unusable.
>>110203863A real language with libraries and tooling that aren't a joke.
>literally another Linux kernel RCE due to a bug in the TCP stack because of the C programming language >something that literally would not happen in Rust>People do AI projects in rust because it's the only language that has ample training set and strong enough compiler to reject many invalid programs>Retards still seething about RustIt's honestly unreal. How long have you retards have rust derangement syndrome? When will you grow the fuck up?
>>110215903The Rust spec is called the Ferrocene Language Specification. It is mostly tied to how rustc works, since rustc is the reference compiler.https://rust-lang.github.io/fls/
>>110216286Well shit, there goes my excuse... but seriously thanks a lot, it's just what I wanted. Bookmarked.
>>110215815use sbcl
>>110215903
>>110209787>still using c, rusttrannyYou aren't writing any C outside of CS50 prajeet singh
>>110215903>rust isnt standardised!!!1!!! ignore the fact that they have only one official distribution that is virtually dominant and a single unfragmented ecosystem, standardisation is only when you are governed by ISO and have your three year drafts that add fuck all rejected over faggot politics over random shit like contracts!!!!1!1!! go back to plebbit midwit
>>110216536C larpers are so delusional it's insaneThey think their shitty ISO paper that often doesn't even have a fully conformant implementation means jack shit against a monolithic unified ecosystem and language
>>110216080C++'s async is such a joke. I'll never understand why they are so obsessed with "backwards compatibility" that they'll add ugly shit like co_ prefixes and refuse to add an async keyword because of the shitty std::async() function they added in C++11. Not to mention not standardising a task type until C++26 while adding coroutines in C++20 leading to everyone inventing their own task types
>>110216536I'll admit I'm a little offended by your canned image response, though I suppose my own complaint was rather generic so I can't really complain.I'm not a C cultist and I'm also quite unhappy with the gaps in the specification. I don't believe C should be used in critical systems but I don't really know what should be used instead. SPARK maybe? Regardless, that's not my concern. I literally only care about having a spec so people can write more compilers for any platform they desire. And as >>110216286 has kindly pointed out, such a thing already exists.>>110216591Believe it or not, I think fragmentation is actually desirable. For instance, I think it's awesome that there are C compilers for platforms like the 6502 and 68000 architectures (which I would never reasonably expect the Rust project itself to support), and I figured I would be more willing to learn Rust if there were more niche compilers like that. I'm just a freak who likes messing around with non-mainstream OSes and architectures for fun.
>>110216536Rust(ferrocene) was certified for some safety critical applications like medical devices and railways.ISO 26262 (ASIL D), IEC 61508 (SIL 3/SIL 4), IEC 62304 (Class C)
>>110216756>For instance, I think it's awesome that there are C compilers for platforms like the 6502 and 68000 architectures>I would be more willing to learn Rust if there were more niche compilers like that.https://github.com/mrk-its/rust-mos
>>110216756>>110217212Also m68k target seems to be supported out of the box on rustc side, you just need g++-m68k-linux-gnu for cross comoilation.
>>110217212>>110217224That's really cool. I was only citing those architectures as examples but I'm glad to see there's already Rust compilers for them too.
>>110211005typing out shitty borrow checker or tokio boilerplate isn't a "skill"
for me, it's Holy C
>>110203754>Both don't have await or async features.>They are garbage.https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/
>>110213317I see. Thanks for explaining.
>>110203754I don't like Rust at all. Specifically, I don't like that it borrows abstractions from functional languages. I don't like types either, nor the borrow checker. To me this is not what the computer revolution was/is about.
>>110203754i like python but honestly all real programs run on c++. or c. anything else is performative. even python scripts end up just facilitating c++ code
>>110203754Also OP, check out Goose. Compiles to C and is faster than Rust on all independent benchmarks. https://kostya.github.io/LangArena/#/top_tabHas no "unsafe" feature and no borrow checker bullshit and no UB and is fully memory safe, unlike Rust that pretends it's safe.And it has "async/await" https://aardappel.github.io/goose/docs/design/coroutines.html#coroutines-stackless-value-typed-scheduled-by-libraries
>>110203754>await or asyncThere has to be a better way.
