Looks like the hype is dying down. All those abandoned projects, no big scale product in prod, people trying to write all sorts of shit in Rust and realizing that it doesn't fit their use cases, all the while the language making it impossible to quickly prototype anything. This language will slowly turn into C++ or simply die. Smart people will just stick to C and modern/safer C++ standards and sanitizers and will keep experimenting with Go/Zig.
>>103249754The fuck do you mean, nigga? I use Zed and Helix and I'm looking forward to COSMIC desktop.
>>103249754The hype is unironically whatever "they" tell you is hyped. Like Mozilla can make a blog post claiming it's uber popular and that's what certain types believe.This is found in all forms of delusion. Trannies, conspiracy theorists, religious people, etc. This is why people think the Central Park 5 are innocent (because a 6th rapist was found to have raped the woman in addition to the others already caught for the gangrape. Remember, nobody disputes it is a gang rape, meaning numerous participants. Thus finding man 6 doesn't exonerate men 1 through 5).
Ah sweet a cnile schizo thread
>Looks like the hype is dying down.conjecture>All those abandoned projects[citation needed]>no big scale product in prodlaughably false>people trying to write all sorts of shit in Rust and realizing that it doesn't fit their use cases[citation needed]>all the while the language making it impossible to quickly prototype anything.[citation needed]>This language will slowly turn into C++ or simply die.conjecture / nocoder talk>Smart peopleameritard nocoder talk>will just stick to C and modern/safer C++ standards and sanitizersconfirmed retard>and will keep experimenting with Go/Zig.maximally retardedand a "posted it again" award to boot.congratulations on your janny "job".
>>103249871hell yeah brother, also have you actually tried Go or Zig? They are pretty nice.
>daily Rust seethe threadMan, cniles have been SEETHING at Rust since 2015, every single day.Everysingleday
All Unix software was developed to assume the lowest common denominator of a teletype output, of course its going to leak memory eventually, no mater what language you use. Even the most formally verified software still has hardware faults to deal with.
>>103249920Oh no, you have to deref a pointer, the whole algo is changed!
the concept of rust isn't bad, but the execution is nastythe concept of just "a low-level language that has an extremely strict compiler and runtime to ensure the programmer cannot make certain mistakes, while keeping the runtime lean otherwise" is not bad, it's quite a useful idea for components that need both high speed and high safety. think networking, for examplein reality however, rust ballooned too quickly and has a lack of standards and is this constantly bleeding-edge (not good for a language for "stability", very not good for a language that requires rewrites constantly). it also has asinine compile times, and its syntax seems to be "different just to be different" as to appease nobodyin addition, it is simply a language with a very small scope. rust makes it IMPOSSIBLE to do any sort of iterative development or r&d, so this throws an insane amount of usecases out of the window, including my own area of expertise (gamedev). these issues however will never be fixed due to the real problemthe community is an insane toxic hellhole, where everyone there sees rust not as a tool, but as their identity. unsurprisingly this means a lot of crossover with other identity warriors like the lgbt (t especially) and the such, but this is just a symptom; the source is just the community seeing rust as who they are, completely forgoing the purpose of programming, being solving problems. tell any rust fan about a problem you face and it will deflect it into a skill issue, show any rust fan writings by someone else about problems and it will deem it propagandait makes it extremely difficult for anyone to even want to bother to climb its insane difficulty curve
>>103249949>dat formal verification
>>103249871>>103249947Nobody uses C. You are comparing autism to autism. Like debating over whether North Korea or Haiti is better or some shit.
>>103249981you cannot guarantee that a dereferencing is not an operationlol what an incompetent
>>103249983Why do you need a standard certification if you can already read the code? Rust does not have multiple competing dialects like C which made standardization necessary?
>>103249997no, except for aeronautics, medicine, fintech, internet infrastructure, embedded, etc... etc...whenever you use a gregarity argument, you immediately lose, anonyou should have known better
>>103250006do you wanna rephrase your nonsensical gibberish again? lmao retard. Stick to python, its more your speed.
>>103250031no, why would i?learn the lingo
>>103250027Yeah, legacy codebase is written in C and Java. It's not written in Rust because it wasn't invented yet.
>>103250013because stability is the one purpose of the language? which means you dont want to have 17 different ways to do async IO, but instead one that's validated and known-good, and wont be deprecated in the next nightly?
>>103247773>that's a difference between how the operators and functions are implemented>>103249833>Operators desugar to something else, even in C, which is the explanation for the == behavior. My claim was that only Rust has this nonsense. So far no one has contradicted it. In other languages (including C, you are wrong about it) both + and == are operators and behave the same way. If in Rust + is a "function" and == is an "operator" and that forces different semantics with references, then that's a Rust specific bad design.
>>103250031>learn the lingoclarif:you will be using it once you start programming
>>103250027None of them use C. You are being lied to. C exists solely because it is legacy and companies can't just fucking nuke 5 million lines of code obviously lol.
>>103250049What does standard have to do with this? What did the standard do to prevent C++ from having 6 different ways to initialize an int? What did the standard do to prevent JS from having 7 different ways to handle an error?
>>103250046not legacygoogle around. then ack
>>103249983>gamedev>solving problems>no real knowledge>inflated sense of self-worth and relevanceevery single time
>>103250040>>103250057You sound a little asshurt. Learn how deref works, better yet, stick at least 5 more years in python and come back to Rust when you are ready.
>>103250069whataboutisms are missing my point. the fact that rust's claim to fame is safety and stability, is opposed by it going down the same path as these other languages
>>103250093It's not whataboutism. I am genuinely asking what stability has to do with standardization? Standards break backwards compatibility all the time.
You're using rust programs right nowhttps://blog.cloudflare.com/how-we-built-pingora-the-proxy-that-connects-cloudflare-to-the-internet/
>>103250089>anon learns that python itself is written in cyour world is a lie
>all those "lets rewrite this in Rust!" projects>none of them complete yet
>>103250122>webshitter langyeah, thats what were saying since a while now
>>103250106standard bodies break backwards compat of existing standards in known, evaluated thought-out means at specific release intervals with clear warning beforehandwithout a standards body, everything is out of standard and one must end up prevailing, causing others to need to rewrite, etc.to be clear i'm not saying that other languages are amazing, if anything it's important to know the limitations of your tools and learn to hate them. it's that with rust you give up so many other things that the payout must be large
>>103249988gem
>>103250076Average Rusttranny response to criticism lmao
>>103250167I am also not arguing rust vs other languages, I am only saying that the only usecase of standard is standardizing something that has multiple competing implementation which Rust doesn't have.It makes perfect sense for C, not so much so in Rust. You can study the behavior of Rust by examining the source.
>>103250122This seems like a good use of Rust, but I feel like most of the perf gain is just the one you tend to get when going from a generic solution (nginx) to an in-house one specifically tailored to your operations
>>103250200>You can study the behavior of Rust by examining the source.This is, in fact, the ONLY reliable way of studying Rust’s behavior. All normal languages, even the hellscapes like JS and Python, have a standard that says “this is how the language works, read this if you’re curious or want to write your own implementation” but crabs say this is not necessary for a language they expect to be used in absolutely mission-critical, must-not-fail, audited-to-hell-and-back contexts like systems programming
>>103250376code is the best documentation.
>>103250398>spend so long screeching at “cniles” about not documenting their work that the complaints can vote and buy cigarettes>write an external standard so that anyone can understand what the fuck a particular piece of code does? lmao no just read the compiler source bro, it’ll make sense just trust me
>>103250443your meme arrows mean nothing. read the code.
>>103249754yeah, its a shit langand the community is trashif either of these statements would be false, rust would have gotten some traction outside of a select few webshitter companies
>>103250066>none of them use Cidk, man
>>103250027They use C++, are you a retarded nigger?
>>103250604>>103250618nuh uhnow shove your foot into your mouth until you choke to death
>>103250618>>103250639and post pics i want to see the whole process
>no picshow disappointing...
>>103249754https://www.theregister.com/2024/11/18/llnl_oxide_compute/>LLNL looks to make HPC a little cloudier with Oxide's rackscale compute platformRackscale computing with Rust underpinnings is helping the US make nukes and keep the ones it has like ah spicy meataball.
>>103250702C can reorder the execution as well. It also offers no constraints on any timings he is talking about.
>>103252516>Instead, Oxide developed its own that runs a Rust-based operating system called Hubris.Well that's interesting, let's check it out...>https://hubris.oxide.computer>about 2000 lines of Rust>no operations for creating or destroying tasks at runtime, no dynamic resource allocation, no driver code running in privileged mode>It has been 61 days since the last Hubris kernel bugSo a tiny operating system that doesn't do anything an operating system is supposed to do, and somehow they still manage to have bugs. Seems like a fun project, I'm happy for them that their startup got funding but this is hardly notable.
>>103252702>anything an operating system is supposed to dodear diary: today anon told me arbitrating between tasks and managing access to hardware resources isn't what an operating system is supposed to do
>>103249997do they have twinks in north korea?asking for a frien
>>103252762Yes anon, your toy kernel that "arbitrates between tasks" but can't create or destroy any is totally a real operating system.2000 lines of Rust is like 10 lines in some other programming language by the way. Which is how much you need to "arbitrate between tasks and manage access" ie run a scheduler and a lock
>>103249905>copecope
>>103249754I'm looking at learning Rust. Generally want to get into systems programming. So have been thinking about C, C++, Go or Rust. C seems fine and good to know, C++ seem like a huge fucking mess and absolutely feels like it was designed by absolute retards, endless versions, endless autism surrounding 'the right way to do things'. Go is made by Google so it's immediately shit and has horrible C++ like syntax. Rust seems good, syntax makes sense and has a whole lot of nice features. Build system and tools are great too. I think objectively just learning C and Rust are the best options here. C++ is too far gone and fuck Google and its Go language.
>>103249754There are two kinds of languages: those that everybody hates, and those that nobody uses.
>>103253005>I think objectively just learning C and Rust are the best options here.I would recommend those two as well. You don't need to write that much C to get a taste for it before moving on to Rust. You'll hit the limits of C quite quickly trying to use C APIs
>>103253005I suggest you learn what is actually used in the real world
>>103253085I already use C# and Swift in my daily work, but I want to start getting closer to lower level languages, as that's where the work will be in the future because everyone only chases web/mobile development.>>103253035Thanks!
>>103253100Yes, I suggest you learn what is actually used in the real world in systems programming if that's what you want to learn. If you do find a job there it will almost certainly be C++.>as that's where the work will be in the future because everyone only chases web/mobile development.lol, no.
>>103253117I don't want to work with C++, because I'm not a sociopath. :)> lol, no.Wrong again.
