> amazon is very concerned over how unsafe rust is> rust's developers are so incompetent that amazon is wanting to pay people to try and make rust less shit and actually safe> "The Rust Foundation has reviewed our plans and agreed to host this endeavor."> "Today, the Rust standard library comprises roughly 35K functions, with approximately 7.5K unsafe functions, and 3K safe abstractions. The core library has 21K functions, with 7K unsafe functions and 1.7K safe abstractions.> "In the last 3 years, 57 soundness issues have been filed in the Rust standard library and 20 CVEs have been reported. Of these soundness issues, 28% of them were discovered in 2024, telling us that the rate of change of the standard libraries is faster and more unsound. Over 90% of Rust based products/services depend on the Rust standard library with virtually every Rust application depending on the core library."as per usual, /g/ was right again about how fucked things are with this language.https://aws.amazon.com/blogs/opensource/verify-the-safety-of-the-rust-standard-library/
>>103321737Based. Rust can't stop stacking the Ws.
I keep telling myself. > Oh, I should switch to rust instead of using C. It will be so much better. Every. Single. Fucking time I do. Shit happens. Why?> "Did I ever tell you what the definition of insanity is? Insanity is doing the exact same fucking thing over and over again and expecting shit to change."
>>103321751Literally first post and already bot response.
>>103321770people here have been pointing out the massive problems with its "safety" claims for a couple of years. rust trannies absolutely lost their minds over it, trying to defend how they can use unsafe functions because a rust tranny said it was safe. it's nice to see that amazon are no longer trusting these fucking faggots to fix their shit.
>>103321770reminder that rust doesn't even have a standard unlike C. they can't decide on one lmao.
>>103321821Right. I never really bought the whole "memory safe" scam they like to shill even though no language can be truly "memory safe". But you know. It was a change of pace. But these fuckers cannot get their shit together. So I am just going to stick with C and not waste my time. Simply put.
>>103321751FPBP cniles seething
>another corporation invests into Rust>cinile shits his bed in utter desperationLove to see it.
>>103321821>people here have been pointing out the massive problems with its "safety" claims for a couple of yearsWhat are the massive problems?>inb4 complete misunderstanding of Rust safety model>rust trannies absolutely lost their minds over itAnd that's why we have daily Rust seething threads on /g/?If anyone is losing their mind, it's the people who can't stop making threads like this.
>>103321911it's funny how Amazon can only seek to benefit Rust by further studying its safety characteristics, and you take this as a win for C???
>>103321737>pay people to make a shit language better instead of just adapting and moving to another fundamentally better language and moving on with business
>>103321737>57 soundness issues have been filed in the Rust standard library and 20 CVEs have been reported.so these were theoretical issues which might affect your program if you used the library in a certain security critical way. are there any real examples of these flaws being exploited?
>>103322151post string manipulation lib of any language that has been mathematically proven to be safeor admit you simply do not know what you are talking about
>>103322118My question is, where did I say that this was a win for C? Or why did you interpreted my statement as that? I was just saying I am just tired of the issues that are involved with the language and want nothing to do with it. I never said that this "was a win for C." Are Rust programmers this retarded?
>>103322177this is you avoiding hypothetical safety issues by sticking with a language that has guaranteed safety issues, no namespaces, undefined behavior in signed arithmetic, inconsistent build system, and on and on and on and oncome the fuck on
>>103322172>nothing else is 100% perfect so you automatically lose>strings are the only problem with rust
>>103322177NTA, but if you are still struggling with Rust even after studying it for some time, then that language is definitely not for you.Either way this thread is about amazon contribution to Rust lang.
>>103322200You completely misunderstood his point. Nice pic, but if you want to post selfies you should go to >>>/soc/
>>103322200post a problem with Rust strings right nowyou are smart enough to find the safety issues, right?
>>103322172You're not wrong to want a formally proven language. Rust is getting close with projects like these:https://github.com/formal-land/coq-of-rusthttps://github.com/model-checking/kani
>>103322199Do you not realize I have a choice right? I don't have to stick to C or Rust. Swift, ADA SPARK, Go, Kotlin, or any other "memory safe" language if it really makes you happy. Hell, I can just say fuck it and write in assembly out of spite once I learn it. I am just tired of being lied to by the people who manages and maintains the Rust language.
>>103322259Who asked?
>>103321737>as per usual, /g/ was right again about how fucked things are with this language.I've been at it for a long time and gave up due to the bizzare comebacks of Rust folks. Good to see that things are healing.
>>103322203I got to be real with you. I barely touched Rust due to the issues that happened a while ago. Such as the trademark debacle, or the rust conference fiasco, or the overzealous marketing.
>>103322280So you come to a thread to give your opinion about a language you haven't even used.Peak /g/ midwit
>>103321751fpbpAmazon spending money and time on formal verification tools and contracts for rust is literally a win and proof rust won. The irony that people ITT don't realize that is hilarious to me.
>>103322320> literally a win> Rust standard library: 7.5k unsafe functions> core library: 7k unsafe functions> a winthis is a massive fail showing just how much rust trannies had mislead people over several years about it's safety. amazon makes it quite clear that the current developers are way out of their league, barely have any idea what they're doing with their patchwork quilt of "trust me bro!" unsafe code and are now desperate for outside help.
>>103322280>Muh heckin trademark fiascoRust doesn't want Debian breaking their software and calling it Rust. Same reason Mozilla didn't want Firefox to be broken by Debian and called Firefox. Stop using shitty distros like Debian or those built on Debian, and you won't have any "trademark" problems.
>>103322348The only one misleading here are brainlets who think unsafe blocks mean the code is unsound.
>>103322104The son looks happy. You must be really low IQ to lack the foresight to see how Rust will make every little part of your software less readable and less maintainable, leading to stagnant ,abandoned, and buggy software (despite brainwashing maybe it will shock you to learn that software can fail to do what you want for reasons other than memory errors. Like 99.999999999% of the time).
>>103322259well you said>So I am just going to stick with C and not waste my time.hence why I mentioned C.>Swift, ADA SPARK, Kotlinmaybe great, idk, never used them. obviously SPARK seems very safe>Golook, I think Go is a pretty solid language but it does not even come close to offering the guarantees that Rust does at compile-time. Rust beats Go at EVERYTHING except for durations of compilation and memory fragmentation (due to having a Go having a GC)
>>103322348>amazon makes it quite clear that the current developers are way out of their league[citation needed]
>>103322348Unlike C, there is a completely normal and standard way to avoid libc without fiddling with compiler options and still having your shitty C compiler inline calls to intrinsics or libc. If you don't trust std::*, don't use it.
>>103322367if one of the biggest corporations on the planet is skeptical about its safety then you're in a world of shit, tranny. seethe harder.
>>103322367this is the same problem that meteorological folk run into with classifying storm levels.
>>103322374If your Rust code is unreadable and unmaintainable then that's huge skill issue and you shouldn't be doing systems programming, or any programming at all. Git gud>inb4 but I don't codeYes, we know.
>>103322348what percentage of code in an average Rust application is marked as unsafe? if C code had to be marked as unsafe in the same circumstances, what would the equivalent percentage be?
>>103322385You are the one who thinks unsafe blocks mean the code is unsafe. No matter how much you want to change the truth, the fact is that you have literally no idea what you are talking about.
>>103322357I should've put links in my response. Which is on me.Here you gohttps://devclass.com/2023/04/11/dont-call-it-rust-community-complains-about-draft-trademark-policy-restricting-use-of-word-marks/https://fasterthanli.me/articles/the-rustconf-keynote-fiasco-explainedhttps://users.rust-lang.org/t/why-is-there-so-much-mismanagement-in-the-rust-foundation-and-core-team/94822https://users.rust-lang.org/t/why-is-the-rust-community-often-so-arrogant/51415
>>103322385Are you actually going to prove your unfounded claims or just continue shitting your pants?
>>103322389It all is. That's why everything made with it is shit and fail like that shit terminal emulator. Is that the only finished rust project that didn't involve slave driving hundreds of people like pharaoh did to blacks when he had them build pyramids in Egypt?
>>103322400None of these I am clicking on as they have nothing to do with Rust the programming language. Seethe more mental midget and reread my post.
>>103322405Amazon is using Rust. Have you even read OP?>inb4 but I can't read
>>103322400>https://devclass.com/2023/04/11/dont-call-it-rust-community-complains-about-draft-trademark-policy-restricting-use-of-word-marks/>rust foundation submits trademark policy draft to ask for feedback>people don't like it>the policy is changedWow, the days of Rust are numbered! It's definitely over for them this time!
>>103321846But anon.. you don't understand, the standard must ACKnowledge my gender floating point number. I am so important uwu.
>>103322413>I can't readEnglish includes the "unsafe" keyword.Rust includes the "unsafe" keyword.Amazon uses English.Amazon uses Rust.Coincidence?
>>103322435>>>/lgbt/
>>103322440No one tell this nocoder about unsafe in other languages.
>>103321770Thank you for your service to our country.
>>103322451>unsafeskill issue
>>103322464That's probably the best reply you could come up with. Congratulations either way.
>>103322472I know, that's why I said it.
>>103321737crabs btfo with grievous casualties
>>103322413Yeah they also fly rainbow flags in Pride month (Pride year when?).Rust is obviously a huge shill-job and its use is akin to a mix between cultism (which ideologies are in any case) and virtue signalling. Something like that... So these bigwig execs read some facts on paper and decree that their "mechanical turk" (lol that that's a real Amazon term) employees must write with it to earn a paycheck.Which is as I have pointed out already, its only use is reminiscent of pharoahs slave-driving the blacks to build pyramids.Outside of this, it has not been used thus far to create anything noteworthy. You have really pathetic abandonware attempts and software that simply isn't very good, because memory safety is like 0.0000000000001% of a piece of software (as mentioned, almost 100% of bugs are because you accidentally omitted some piece of logic, which is harder to do in syntactically clean languages).Let's take a look at the retarded gopher depicted beside the enraged C coder (programmer is a compromised word due to programming socks memes), well, his threads are filled with links to 4chan users' finished softwares which are fully functional. Yes even a 4channer can make a fully featured and working piece of software in Go (and in Python too, no doubt).
>>103321737>In the last 3 years, 57 soundness issues have been filed in the Rust standard library and 20 CVEs20 CVEs in 3 years is actually incredibly low.
>>103321737What do you need 35k functions for? Are these different shades of dilators?
