Yeah. But seg faults are great! You get into trouble when the memory bug keeps you on the same page and that page also holds sensitive data or a function pointer that is permitted to escape that page. What we're really talking about is the vulnerabilities inherent in cloud applications. If you don't own your hardware and you let public users install programs on shared systems without admin supervision you're ALWAYS gonna have problems. There's no technical solution here. It's the architecture of the attack surface they've selected... oops.
Jesus Christ is coming back soon, repent from your sins and believe in the gospel. Jesus loves you and wishes that none would perish but that all would come to repentance. He died on the cross for your sins, so that through him you may have eternal life. This could be your last chance to be saved❤️
There are already no seg faults in Government software. No one is using C/C++ in the Government for projects outside of DoD, and even then you had smart pointers since C++ 98 which pretty much kills the whole argument for migrating to Rust....also...Rust doesn't not have an ABI. That's a problem.
10:56 "the rust compiler will not let you compile code that isn't memory safe" Unless you're a Chad and all your code is one big unsafe block, like god intended...
Remember how just a few months ago ferrocene was not industry ready, and suddenly it got approved for medical software out of the blue without actually passing any safety and soundness tests? Yeah, now it all makes sense... considering how Rust is not a language specification but completely relies on its (few) compiler implementations, I wouldn't be surprised if this push has happened due to how easy it was to put a backdoor in the language. After all, there's only like 2 compilers they had to make it into to achieve this lol...
It's not just the compiler, but there's the human aspect to it. Communities, foundations, grants, etc, all are vehicles for government money and through that for top-down control.
@@houssamassila6274 C++ is nice and you can write memory-safe code in it. Just most of the people are not good programmers and they write stupid code. I see this every day in Java as well. Especially the code written by programmers in India. But yeah, they are cheap, so the company thinks they save money.
We’re going to build a big beautiful Modula compiler, like no one has ever seen. Maybe you’ve heard of Delphi? Well this will make that look small and slow in comparison. Everyone will be talking about it.
I work for a federal agency that has some of their own applications written in-house. It's some of the trashiest stuff I've ever seen. It's literally a meme between me and my coworkers how often it goes down. The federal government is utterly incapable of managing simple internal software for absurdly basic tasks. An endorsement from them is laughable.
@@parito5523 Record keeping and databasing with extra features specific to the task. Can't be specific but it's about as technologically complex as a search engine website from 2006. Visually looks like it too lmao Best part is there's a massive team of contractors "supporting" it and releasing microscopic builds all the time yet it never seems to actually become more reliable
@@parito5523I work in Healthcare, not govt but govt adjacent. A lot of our in house code is written "to keep our solutions proprietary" even if it's worse than the open equivalent
White house currently believes the best way to be memory safe is to have no functioning memory in the oval office. Cannot overrun the buffer that doesn't exist.
But he'll win again because 59% of Nikki Haley voters will not vote for the former guy because he is a criminal. I'd rather not have a criminal who likes Putin.
@@CjqNslXUcMyou have to look at the data that the "experts" are presenting, to see if it is valid. Today, any idiot with the "correct" opinions can be called an expert by the mainstream media, especially in more subjective areas like politics and economics.
@@rj7250a The problem with that idea is that you're likely not even close to being qualified to evaluate evidence yourself. You don't know statistic methods, experimental design, or relevant background information. You can easily find studies that seem to confirm any preconceived idea, especially if relevant to a political issue. "Doing your own research" is a meme. It's what whack jobs use to defend their inane theories. They learn slightly more than the average joe from a few google searches and then debate people who are equally unqualified. If you want to know the truth of a scientific matter without spending years getting an academic degree you need to use reputation as a epistemological measuring stick. That's just how it is. Listen to the majority of people who are actively working and publishing in a field. Read literature reviews and meta-analyses in high-impact journals. Don't be an arrogant idiot. If there's an opinion you have that diverges from the scientific consensus, you're almost certainly wrong.
@@rj7250a You're likely not even close to being qualified to evaluate most evidence yourself. You don't know statistic methods, experimental design, or relevant background information. You can easy find studies that seem to confirm any preconceived idea, especially if relevant to a political issue. "Doing your own research" is a meme. It's what whack jobs use to defend their inane theories. They learn slightly more than the average joe from a few google searches and then debate people who are equally unqualified. If you want to know the truth of a scientific matter without spending years getting an academic degree you need to use reputation as a epistemological measuring stick. That's just how it is. Listen to the majority of people who are actively working and publishing in a field. Read literature reviews and meta-analyses in high-impact journals.
@@twelveticanthats objectively wrong. c++ is actually a pretty safe language, as long as you stick to like c++11 or newer, and ignore some of the more raw functionality it inherited from c. stop spreading misinfo about the language. c++ is a very powerful language and absolutely safe in tandem with a brain.
and I will also ask, why is this coming out now? what happened to the last 50-80 years of their space programs and other programs that NEED a programming language?
@@NormCantoral there are planes flying with floppy disks at this very moment. Aerospace on the computer side lags like 20-30 years behind due to safety requirements.
And Boeing attempted to use Java for a critical control system which ended up insanely unsafe. In physical testing the landing gear would randomly fail to go down or come up... because the decidedly non-deterministic garbage collector blocked the signal interupt. (Not to mention systems complex enough to use the JVM are right out of the gate inherently non-realtime and near impossible to formally validate.)
The fact I have the presidents sons apple phone archive I can literally use software and an extra iphone to turn it into his physical clone of his phone is proof our country is a joke. Anybody can download it and see what they did to his family members and many felonies including being a traitor 😂😂😂 shyts not a joke the world is fked.
@@justsomeonepassingby3838 just google hunter Biden iPhone archive it was on 4chan for a whole week but news dies down and people stop caring. You can find it online if you really wanted it. It was publicly leaked.
Funniest part about this is that one of the few programming projects I did in college was a very tight memory manager simulator written all in C++ of course.
@@plainenglishh key word is 'usually'. Exercise is common sense... but I'm pretty sure soon there will be a clause somewhere that overweight body positivity is more important than exercise due to factors of social stigma, unnecessary physical and mental strain, etc. As for the regulated consumer diet, check out "Everything I want to do is illegal" by Joel Salatin.
I learned to code for fun in high school, I didn't even know it was a job. I'd never heard of anyone who got paid to code, I assumed it was like 3 people who worked for banks and that was about it.
@@XxZeldaxXXxLinkxX Most software is so simple nobody who does programming would have had to made it. There's an enitely plausible world where WYSIWYG dominates even business logic. I'd still consider it programming but I can see how some might now.
Fun story, Mozilla switched FF to Rust and now I get (very slow) memory leaks. (I use a lot of tabs and keep a window open for days on end.) Even though it needlessly forces reloading of some dynamic pages when using the back button rather than simply retaining the state. (Why that reload doesn't flush the memory leak?) When did a few memory leaks become the sole definition of unsafe? This also reminds me of the old saying that generals are always fighting the previous war (they fix what they did wrong the last time but the world has already moved on). All of the comparisons with other languages that I see Rust evangelists make would have been valid arguments cira 1995, but it isn't 1995 and the real problems are in management anyway. When nobody in charge understands the basic idea of real critical systems, "real time", or a fully validated deterministic system, then no amount of language level "memory safety" is going to save you. ("real" system as in actual specific hardware part numbers with performance limits and requirements. Opposed to some abstract machine that theoretically yields a "correct" answer even if it takes an unknowable amount of time.) This Rust thing is like the systems they sell to companies, eg "lean" "5s" "6sigma", "agile", etc (basically the corporate equal to the old get-rich-quick infomercials selling you a system for flipping real estate.). They aren't bad systems, but there is no magic and any competent management would already be using their own version of the components anyway because it's just a rational way to conduct business. Meanwhile, incompetent management who could benefit have already proven they are too lame to implement such obvious system procedures.
my view is no one should be using dynamic memory in modern C++. Theres fundamentally no need to just be allocating objects via new in the current day. Only scenarios where I can see it as legitimate is, you need to allocate some buffers, or you have virtual functions and need to do base pointer polymorphism on some objects. In the former, you can do it via straight C++ and let it get RAII'd away. A vector of char as an example and then slice it up. regarding the later, its quiite literally 90's boomerisms of C + Java style C++. theres things with mmap, i make alot of huge page data structures like ring buffers and whatnot so using raw pointers there, but its really just a matter of allocating a few GB up front, get it into the TLB, and then use it as a packet buffer pool or ring buffer, but smart pointers do nothing for you there
yeah as long as you use the slow complex new features that still dont completely enforce memory safety because adapting to a new language that was built from the ground up to prevent bugs while remaining just as fast as other non memory safe languages is hard because tradition
@danielhalachev4714 I don't understand these people. All were asking is for them to do a complete reading of the Rust compiler source code and figure out if there's any deliberately hard to spot security vulnerabilities. It's only 2 000 000 LOC of .rs files. Easy. Why do these people complain like the only way to use others software is trust when presented with decently sized projects like this?
The claim that the borrow checker is difficult to work with is overblown, unless you're really doing something tricky. I had an issue with an iterator that I solved by keeping temporary values in an arena until I was done with the iterator.
Welcome to coding and closed/open sourced projects in the twenty-first century, people without a personality inject their politics when they should be doing their jobs.
@@dmitriidemenev5258 if you know you know if you don’t you don’t. In the case you know, nothing either of us will say will convince the other. If you don’t know, then you should experience it yourself and formulate your own opinion. There is a reason rust community is mock, and openly.
I think that people who learn anything without any passion and just because their only interest is money, not going to learn Rust. They will give up on chapter 4 of The Rust Programming Language. There are easier ways to get the same salary in software.
An article I saw about this urged to not be blind to the fact that although 3 of 4 exploits found are related to memory safety, only a very small fraction of the real worst cybersecurity exploits discovered had been related to memory safety. Either way I hope rust gets developed further.
I wanted to investigate the rusty shackleford programming language but there was some controversy a few months back, so I went with Zig and I think Go is another one I need to try out.
That was a underflow bug in his agressiviness status, not memory corruption. Rust also disables over/underflown checks in release builds, because those checks are super slow.
To add a small pedantic correction. Writing Go is certainly simpler than writing Rust, but it does not take less lines of code at all. Go is very easy to learn and write, but it's hella verbose when compared to functional or functional inspired languages, like Rust
This joke has multiple layers in multiple directions, ranging from psy-ops and built-in backdoors (which itself can be made into a joke about being gay) to definitely not gay for Astolfo and anime "slurs" that the resident twitter furry population has coined.
You might be joking, but that's actually true. Any new techniques and stuff the 3 letter people couldn't fit in C/C++ compilers, and now it's difficult to shove them in there without a good excuse, those are all in the Rust compiler. They even tell you this in the name - Rust. Not to mention the crate/npm like system, nah thanks.
I would think that most space systems would be written in Verilog or VHDL and then made into hardware or used on FPGAs, no? If you want robust, failsafe, memory-safe, anti-fragile, efficient, minimal, and fast systems, the best solution is hardware languages.
You can write memory safe code with C, is not really hard, what people complain about is that the compiler doesn't check it before producing the binary, with Rust you are forced, however there are external verification systems like Coq that can check if the C program is memory safe. So this analysis really comes from someone who has little to no idea about programming languages.
Even if verification software is as good as the borrow checker (probably isn't), you're still wasting time on extra passes and testing that comes after compilation when you could just have the Rust compiler verify the code right away.
@@Abu_Shawarib you don't even know what you're talking about (obviously) stating shit like "probably". yea me too, I have no idea about C, rust, coq, and it fucking pisses me off that people just have this mindset of "oh, I know it all better, so it maybe has to be how I think it its, so I am not even going to bother to look into whatever the fuck you said" not calling you out, but everyone who thinks this way, and I genuinely believe that this is a wrong mindset to have. be open. try new things. and remember, everything in life is a skill issue. using C? skill issue. using rust? skill issue. shit talking other programming languages? skill issue. (aint no way I actually just send this garbage piece of a random comment out into the vast wide world of web... )
Regardless it's not hard to implement best practices, like paying attention to any causea buffer overruns or allocated memory. Otherwise it's like saying blueprints should be banned because you can draw up a building structure that's unsafe. That's why you get people that know what they're doing.
The "no GC" requirement is wrong, demonstrably so, since Java (and a VM) has been used for decades for satellites and even interplanetary craft. It's also a bit of a non sequitur, as whether or not something is using GC is a matter of perspective; e.g., you've delegated a scripting language or DSL to run on a VM or embedded in C/C++.
0:35 Man I understand the need for a concise video. But I think the context of them having excluded all GC languages because they're doing space software is very important context.
You know Rust doesn't do any memory management, right? If you were talking about a garbage collected language like Go, C#, JS, Python, etc. you might have a point.
Bro you're just falling into the compiler backdoor theory The idea of a self replicating self hiding compiler backdoor that's impossible to detect and injects itself into anything you compile. Aka there's no damn point because there's nothing you can do at that point anyways
@@UNcommonSenseAUS it would've been in LLVM if they did. Meaning C C++ and the rest are just as backdoored How about thinking about the feasiblity of such things before being adamant about shit
Shadow stacks solved like 90% of the problems rust claims to solve whilst not forcing you to engage with a language only good enough for tiny projects.
Many memory safety vulnerabilities lead to logic errors, like privilege escalation or reading attacker-controlled files or something, not just instant RCEs of the type a shadow stack can prevent. Rust isn't 'only good enough for tiny projects' lol - Firefox's rendering backend, half of Google's Fuchsia OS, the Deno JS runtime, there are some pretty big projects written in Rust. Huge companies like Microsoft, Google, Amazon, and now the US Govt are talking about doing even more, do you think they just haven't noticed it's useless?
You'll never see one because Rust is a research language being maliciously represented as a production language. Its designer wants to be able to add whatever new feature strikes his fancy whenever he wants, and to remove it whenever it turns out to have been a bad idea, whether it breaks your code or not. This is fine if it's explicitly a testbed for new ideas, but not if it's for writing serious software that people actually depend on. C, C++, Fortran, Pascal, Eiffel, all these languages have standards and guarantees that if they're going to deprecate a feature and later remove it, you'll have plenty of warning, often on the order of a decade or more. This means that once code becomes functionally complete and all known bugs have been fixed, you can leave it alone for years and it will keep working. Imagine writing an OS kernel in Rust. You'd write a driver for the PC speaker, whose specification has been static for decades, get all the bugs out, and then have to rewrite it every time the language spec changes and your code won't compile anymore. And the designer *likes* it this way.
@@yoshikagespeedwagon8025 Rust *cannot* guarantee memory safety. There exist operations that are both necessary and inherently unsafe, which you would have to implement with an unsafe block in rust. If you're giving up the entire point of rust, why bother with the overhead instead of just using C? Rust is awesome and the majority of software would be better off running on it, but only using rust is foolish.
Considering the CVE count and how many of them aren't exploitable I think this whole thing really has gone far enough. The biggest risks are still inadvertently public functions. Not sending a magic packet to a webserver and getting root access. That's a problem programming languages actually can help with but they simply aren't. Especially if you're accepting friction on the level of Rust.
The economy can speak louder than the white house. You gotta give incentives for things to be grabbed when there's other options. Rust is giving me COBOL vibes now. I have in the past mocked the "rust community" because of their overly.. You know.. More suspicious about anything the small G endorses (not joking). Maybe it's just slower for new languages to catch on? We tend to prioritize efficiency and time. I also have heard of memory issues even after compiling though but I haven't confirmed and not a programmer. For Rust to be more implemented with niche critical systems, maybe that makes more sense? Can anyone else give me more insight into understanding this?
Rust is great for the right usecases. It has an extremely steep learning curve compared to other languages to get up to speed in productivity, but for critical software it is absolutely recommended. It is much much easier to write safe and maintainable code than C++ due to less verbose syntax, enforced memory safety and enforced error handling and matching patterns. But you can absolutely write unstable and unsafe Rust (unwrap everywhere, unsafe blocks). Rust should not be used everywhere though. In essence: If a Rust pro and a C++ pro would write the same critical code, the Rust code will be more trustworthy.
Have they ever heard of the "Safe C" library? On top of that, modern C++ is fairly safe. Rust limits your creativity. It should be on the list of recommendations, but not be the only recognised language. For some other tasks, other languages are required. VHDL, HDL for FPGAS, Ladder Logic for PLCs, MOJO PYTHON for AI, C/C++ for embedded systems, Zig for overall convenience, portability and backward compatibility with older languages, ASM for critical blocks of library development for system driver development/embedded C, the list will grow. Then, not all projects will start rewriting their codebase because the government is doing their space and AI stuff in Rust. Think of Adobe and Autodesk. Probably the parliament/congress is finding avenues to spend money on contracts and tenders. The initiative will ultimately go nowhere. I'm not excited at all. I had a notion that only the Government of India has always been incompetent in all aspects of technology and even administration. No! I was wrong. America is no different. BTW, I prefer Rust after C. It's still easier than other high-level languages out there.
I'm kind of torn on this topic. I just started learning Rust a couple months ago because I wanted to do something different from C but I still want to work more on the lower level. I think its basically un-enforceable to make people write code in a certain language in general, but of course they could try, especially if it's government software. Immediately when I see this kind of recommendation coming from the government, I think what they have to gain from it. Some people have brought up the idea of a backdoor in one of the languages they recommend (like Rust), but that seems pretty difficult given the language is open-source. And if one major open-source software is compromised, then following that logic none of them are safe. But that's not the discussion here. My very naive prediction is that this isn't really gonna do much except maybe increase some Rust jobs. It's not like you can just stop writing things in C++ or C, especially since there is so much of that code which already exists.
Also I will add the fact that Rust will never replace C. EVER. People forget that the reason why C is so ubiquitous and hasn't been dethroned for what it does since it's inception 50 or so years ago. C is more or less high level assembly with all that comes with it.
I can only imagine how many schizos are on the Chans freaking out because the NSA recommended Rust. Now we're going to see Rust software re-written in C.
You will have no segment faults and you will be happy - Government
Eat the bugs. Inject the Rust to keep your projects safe.
Yeah. But seg faults are great! You get into trouble when the memory bug keeps you on the same page and that page also holds sensitive data or a function pointer that is permitted to escape that page. What we're really talking about is the vulnerabilities inherent in cloud applications. If you don't own your hardware and you let public users install programs on shared systems without admin supervision you're ALWAYS gonna have problems. There's no technical solution here. It's the architecture of the attack surface they've selected... oops.
Shame... Getting random segfaults from software that isn't mine was always so exhilarating.
Jesus Christ is coming back soon, repent from your sins and believe in the gospel. Jesus loves you and wishes that none would perish but that all would come to repentance. He died on the cross for your sins, so that through him you may have eternal life. This could be your last chance to be saved❤️
There are already no seg faults in Government software. No one is using C/C++ in the Government for projects outside of DoD, and even then you had smart pointers since C++ 98 which pretty much kills the whole argument for migrating to Rust....also...Rust doesn't not have an ABI. That's a problem.
10:56
"the rust compiler will not let you compile code that isn't memory safe"
Unless you're a Chad and all your code is one big unsafe block, like god intended...
Rust is CIA n1gerl1icious code.
ur based asf, but this defeats the entire purpose of rust!
@@hakdergamingnah, he'd pop off
why is it always people who dont even program talking about "muh unsafe", dude you dont know what fucking threads are, shut up
Tru
NSA Rust back door soon in 2025.
Rust gives really good safety guarantees against memory vulnerabilities. This is a big class of vulnerabilities but it is not comprehensive.
Remember how just a few months ago ferrocene was not industry ready, and suddenly it got approved for medical software out of the blue without actually passing any safety and soundness tests? Yeah, now it all makes sense... considering how Rust is not a language specification but completely relies on its (few) compiler implementations, I wouldn't be surprised if this push has happened due to how easy it was to put a backdoor in the language. After all, there's only like 2 compilers they had to make it into to achieve this lol...
@@tiranito2834 Seek help from a psychiatrist
It's not just the compiler, but there's the human aspect to it. Communities, foundations, grants, etc, all are vehicles for government money and through that for top-down control.
I mean, putting in a backdoor into open source language is probably not that easy
State mandated homosexual software
what the hell does that even mean lmao
Autistic too
@@iliashdz9106 Gay programming
@@iliashdz9106he doesnt know
@@iliashdz9106it means input get with inputs & outputs get with outputs
I want this to feature prominently in the debates. I need to know Trump's opinion on C++.
Trump seems like a Java guy to me ngl
One of them should memorize an answer and have someone ask the question in front of a camera.
C++ is a tremendous language, it's yuuuge.
@@houssamassila6274 C++ is nice and you can write memory-safe code in it. Just most of the people are not good programmers and they write stupid code. I see this every day in Java as well. Especially the code written by programmers in India. But yeah, they are cheap, so the company thinks they save money.
We’re going to build a big beautiful Modula compiler, like no one has ever seen. Maybe you’ve heard of Delphi? Well this will make that look small and slow in comparison. Everyone will be talking about it.
I work for a federal agency that has some of their own applications written in-house. It's some of the trashiest stuff I've ever seen. It's literally a meme between me and my coworkers how often it goes down. The federal government is utterly incapable of managing simple internal software for absurdly basic tasks. An endorsement from them is laughable.
What sort of basic tasks would need in-house softwares?
@@parito5523Basically Security and Trust issues, that's why in house software better
@@parito5523 Record keeping and databasing with extra features specific to the task. Can't be specific but it's about as technologically complex as a search engine website from 2006. Visually looks like it too lmao
Best part is there's a massive team of contractors "supporting" it and releasing microscopic builds all the time yet it never seems to actually become more reliable
@@parito5523 Providing nicer interfaces that interact with old 3270 green screen applications via screen scraping.
@@parito5523I work in Healthcare, not govt but govt adjacent. A lot of our in house code is written "to keep our solutions proprietary" even if it's worse than the open equivalent
I thought you meant rust like the video game
I love that now when I search for things related to rust I actually get results for the language, a couple years ago everything was that game
@bingus_supreme_
I wonder if you actually have a bingus and if so can you please advise on the bingus
got any extra cloth?
No u don't @@MentalOutlaw
It took me 4 minutes and reading this comment to understand he wasn't talking about the game 😂❤ I just smoked some medicinal legal
White house currently believes the best way to be memory safe is to have no functioning memory in the oval office. Cannot overrun the buffer that doesn't exist.
Underrated comment.
I, for one, look forward to having one fossilizing president rather than the other fossilizing president.
But he'll win again because 59% of Nikki Haley voters will not vote for the former guy because he is a criminal. I'd rather not have a criminal who likes Putin.
too many dangling pointers in the presidents mind.
@@Hotshot2k4"None of these candidates" versus "Uncommitted" 2024!
Only good reason to use Rust is to make sure that the outsourced Indian devs don't bring too many security flaws.
Development work done for US govt. if classified must be done in the USA
Security flaws come with cheap cost buddy, pay the top dollar and we'll write you memory-safer code even in c++😉
@@lego46143 Most of it isn't classified and holds personal data.
Security flaws mostly come with the cheap cost, pay the top dollar and we'll write you memory-safer code even in c++😉
@@lego46143 Not if contractors outsource the work of their contracts, as has been happening.
If you really wanted to use a memory-safe language that has been proven in aerospace, you could use COBOL. 🤪🤪🤪🤪
cobol deez nuts, brother
And they are hiring! It is basically a guaranteed job if you can pass a security clearance.
This message is not a government psyop.
You spelled Ada wrong.
Why not Modula-2 or T?
@Sv5YpWTwd9otTA4So83f what is the issue with chatgpt not understanding it
5:44 "According to experts" as DateRightStuff says :"Studies showed that experts follow who fund them more".
what a dumb statement
@@CjqNslXUcMyou have to look at the data that the "experts" are presenting, to see if it is valid.
Today, any idiot with the "correct" opinions can be called an expert by the mainstream media, especially in more subjective areas like politics and economics.
@@rj7250a The problem with that idea is that you're likely not even close to being qualified to evaluate evidence yourself. You don't know statistic methods, experimental design, or relevant background information.
You can easily find studies that seem to confirm any preconceived idea, especially if relevant to a political issue. "Doing your own research" is a meme. It's what whack jobs use to defend their inane theories. They learn slightly more than the average joe from a few google searches and then debate people who are equally unqualified.
If you want to know the truth of a scientific matter without spending years getting an academic degree you need to use reputation as a epistemological measuring stick. That's just how it is.
Listen to the majority of people who are actively working and publishing in a field. Read literature reviews and meta-analyses in high-impact journals.
Don't be an arrogant idiot. If there's an opinion you have that diverges from the scientific consensus, you're almost certainly wrong.
@@rj7250a You're likely not even close to being qualified to evaluate most evidence yourself. You don't know statistic methods, experimental design, or relevant background information. You can easy find studies that seem to confirm any preconceived idea, especially if relevant to a political issue.
"Doing your own research" is a meme. It's what whack jobs use to defend their inane theories. They learn slightly more than the average joe from a few google searches and then debate people who are equally unqualified.
If you want to know the truth of a scientific matter without spending years getting an academic degree you need to use reputation as a epistemological measuring stick. That's just how it is. Listen to the majority of people who are actively working and publishing in a field. Read literature reviews and meta-analyses in high-impact journals.
@@CjqNslXUcM well they did sound like they had an interest in pushing rust. no actual arguments against modern c++ being superior to rust.
still gonna use C
@@twelvetican stop telling people how to develop software :)))
@@twelvetican People like you are why Wine will always suck. Hint: Windows' usermode is object oriented.
@@KookoCraft segfault
@@twelvetican no, you are going to use brainfuck and lolcode. no discussion.
@@twelveticanthats objectively wrong. c++ is actually a pretty safe language, as long as you stick to like c++11 or newer, and ignore some of the more raw functionality it inherited from c. stop spreading misinfo about the language. c++ is a very powerful language and absolutely safe in tandem with a brain.
*FORTRAN90/2003/2021 is also memory safe and always has been*
If the government recommends a specific technology, I start suspecting about it immediately.
Don't worry, Rust totally won't awaken your inner desire to get backdoored by Uncle Sam.
@@ordinaryhuman5645 Well the government fucks me very day so I'm already pretty much backdoored by it :P
and I will also ask, why is this coming out now? what happened to the last 50-80 years of their space programs and other programs that NEED a programming language?
@@NormCantoral there are planes flying with floppy disks at this very moment.
Aerospace on the computer side lags like 20-30 years behind due to safety requirements.
The tech or the recommendation? Because Rust is both safe, practical and fast.
I'm not sure I want to take endorsments from the white house tho
yeh, feels like they'll be rolling out robo-Fouchi to convince us to "trust the compiler" in short order
@tripplefives1402if that misspelling was an intentional BASIC pun...😂
If you don't control memory access, who does?
@@mattmill30There's already "security" cores running on any CPU that's newer than 15 years old. If they want your data, they have it.
@@mattmill30”ken” has entered the chat. And your Unix server.
Let's not forget this was a huge selling point for Java back in the day.
And Boeing attempted to use Java for a critical control system which ended up insanely unsafe.
In physical testing the landing gear would randomly fail to go down or come up... because the decidedly non-deterministic garbage collector blocked the signal interupt. (Not to mention systems complex enough to use the JVM are right out of the gate inherently non-realtime and near impossible to formally validate.)
yes, simple fact is that c++ has proven to be effective for 40+ years and rust hasnt :\
@@pyyrr 40+ years of avoidable damage caused by c++
The main selling point was:
"Compile once, run everywhere (, where a java runtime is available)"
@@pyyrr effective but unsafe, which is the whole convo about
I never expected you to say "fruit drawing algorithm"
😂😂😂😂
Endorsed by the White House?
Alright time to learn Nim.
agreed. 99% sure that this will not end well for any group of people who get involved with this.
@@NormCantoral they were already not ok when they trademarked every variation of rust logo and made programming about politics
Zig
So just because it got endorsed, you're going to use a worse language?
@@antifa_communisthow nim's worse exactly?
holy c is better
C, the refined cougar of programing languages
We don't all have the gift of programming in it
Rust: endorced by the white house
Holy C: endorced by literal god himself
Yes.
TempleOS is the truest Operating System that only the most elite programmers use.
You know who isnt memory safe? 🙂 Hunter Biden, its time to get him a new laptop
The fact I have the presidents sons apple phone archive I can literally use software and an extra iphone to turn it into his physical clone of his phone is proof our country is a joke. Anybody can download it and see what they did to his family members and many felonies including being a traitor 😂😂😂 shyts not a joke the world is fked.
like father like son they say...
@@veryfrozen3271Do you know where this data can be downloaded ?
@@veryfrozen3271Sauce ?
@@justsomeonepassingby3838 just google hunter Biden iPhone archive it was on 4chan for a whole week but news dies down and people stop caring. You can find it online if you really wanted it. It was publicly leaked.
Mandatory Boomer joke: More like, the White House should make Biden's memory safe, heyyyoo!!
His memory is safe already, it purges right away. Sometimes even mid-sentence but that's a glitch they'll iron out in Biden 2.0
C++-ing even harder cause now its rebellious
They told me to stop hitting myself in the face with a shovel, but I'm a rebel!
@@chrimony kick ass non sequitur
@@exoZelia Is it?
@@chrimony Yes, because good C++ is safe. I don't need fucking handrails since I know how to manage my memory properly.
@@Superchunk-k2h C++ is a monstrocity. You can write "good" code in any language. That doesn't mean the language is safe or appropriate.
Funniest part about this is that one of the few programming projects I did in college was a very tight memory manager simulator written all in C++ of course.
Ok what backdoor have the NSA managed to sneak into Rust?
biden memory is not safe
Alexa, play "Rust in Peace" by Megadeth
Utterly based
When something is government recommended there's usually a catch.
🙄
government recommends exercise and a varied, balanced diet... must be a catch...
@@plainenglishhof course, because why it promotes processed bs and fast food at the same time?
@@plainenglishh key word is 'usually'. Exercise is common sense... but I'm pretty sure soon there will be a clause somewhere that overweight body positivity is more important than exercise due to factors of social stigma, unnecessary physical and mental strain, etc. As for the regulated consumer diet, check out "Everything I want to do is illegal" by Joel Salatin.
The government recommends that you change your socks at least once a day.
I learned to code for fun in high school, I didn't even know it was a job. I'd never heard of anyone who got paid to code, I assumed it was like 3 people who worked for banks and that was about it.
If you knew how to code, it never crossed your mind to think about who made literally every piece of software you used?
I used to draw boobs for fun now i get paid for it
actual retard here
@@XxZeldaxXXxLinkxX Most software is so simple nobody who does programming would have had to made it. There's an enitely plausible world where WYSIWYG dominates even business logic.
I'd still consider it programming but I can see how some might now.
@@0xCAFEF00DYet, 99% of it is made by programmers who get paid okay-ish programmer salaries. So there might be something about it after all.
What is more safe: writing code in a language a lot of bugs are known in or writing code in a language not a lot of bugs are known in.
Fun story, Mozilla switched FF to Rust and now I get (very slow) memory leaks. (I use a lot of tabs and keep a window open for days on end.) Even though it needlessly forces reloading of some dynamic pages when using the back button rather than simply retaining the state. (Why that reload doesn't flush the memory leak?)
When did a few memory leaks become the sole definition of unsafe?
This also reminds me of the old saying that generals are always fighting the previous war (they fix what they did wrong the last time but the world has already moved on). All of the comparisons with other languages that I see Rust evangelists make would have been valid arguments cira 1995, but it isn't 1995 and the real problems are in management anyway.
When nobody in charge understands the basic idea of real critical systems, "real time", or a fully validated deterministic system, then no amount of language level "memory safety" is going to save you. ("real" system as in actual specific hardware part numbers with performance limits and requirements. Opposed to some abstract machine that theoretically yields a "correct" answer even if it takes an unknowable amount of time.)
This Rust thing is like the systems they sell to companies, eg "lean" "5s" "6sigma", "agile", etc (basically the corporate equal to the old get-rich-quick infomercials selling you a system for flipping real estate.). They aren't bad systems, but there is no magic and any competent management would already be using their own version of the components anyway because it's just a rational way to conduct business. Meanwhile, incompetent management who could benefit have already proven they are too lame to implement such obvious system procedures.
Firefox mentioned RAAAAHHH
kind of disappointed here. I was completely ready for you to make fun of this press release.
They've replaced him
Modern C++ is also memory safe as long as you use smart pointers.
c has issues like no native builder or package manager
Smart pointers have basically zero guarantees relating to memory safety, so no. It makes it harder to use after free, but that's about it.
my view is no one should be using dynamic memory in modern C++. Theres fundamentally no need to just be allocating objects via new in the current day.
Only scenarios where I can see it as legitimate is, you need to allocate some buffers, or you have virtual functions and need to do base pointer polymorphism on some objects.
In the former, you can do it via straight C++ and let it get RAII'd away. A vector of char as an example and then slice it up.
regarding the later, its quiite literally 90's boomerisms of C + Java style C++.
theres things with mmap, i make alot of huge page data structures like ring buffers and whatnot so using raw pointers there,
but its really just a matter of allocating a few GB up front, get it into the TLB, and then use it as a packet buffer pool or ring buffer, but smart pointers do nothing for you there
Ye but we are pretending that using new language features is harder than using whole new language.
yeah as long as you use the slow complex new features that still dont completely enforce memory safety because adapting to a new language that was built from the ground up to prevent bugs while remaining just as fast as other non memory safe languages is hard because tradition
Sorry, I prefer staying in C/C++, thanks
And I prefer horse and wagon
@@daniel29263that's not memory save, horses have a big head - but their buffer can be overflown with carrots and other hacker exploits
@@daniel29263 Those are just gimmicks, sonny.
Just use your own legs to walk.
crustaceous dont want you to know this but if you just turn some compiler configurations on you get the "memory safety of rust" in any language
I was completely against the idea of the government telling me what programming languages to use, but all that changed at 7:06.
So, how many back doors do they have in Rust
It's open source
@@BSentawhich doesn’t mean there are no backdoors though
@@BSentaif I write a backdoor and make it open source is it suddenly not a backdoor?
@danielhalachev4714 I don't understand these people. All were asking is for them to do a complete reading of the Rust compiler source code and figure out if there's any deliberately hard to spot security vulnerabilities. It's only 2 000 000 LOC of .rs files.
Easy. Why do these people complain like the only way to use others software is trust when presented with decently sized projects like this?
@danielhalachev4714bEcOs US bAd . It’s probably bait tho.
I've recently been learning rust bc I like wasting my time despite having a lot of debt so this is good to hear
When the US manages to stop buffer overflowing the budget I'll care about what they have to say about security.
Meh it's just Monopoly© money at this point anyway. There hasn't been legitimate legal (constitutional) US currency since the early 20th century. "US treasury" notes were all replaced by private "federal reserve" notes (They kept the design static during the transition, other than changing the fine print.). Then Nixon fully legitamized the counterfeiting, and monetary inflation has been transfering massive wealth from the small folk to those on top ever since.
(Article 1 Section 10.
No state shall ... make any thing but gold and silver coin a tender in payment of debts; ... )
The claim that the borrow checker is difficult to work with is overblown, unless you're really doing something tricky.
I had an issue with an iterator that I solved by keeping temporary values in an arena until I was done with the iterator.
I hate rust because of the community behind it. They are so up their own a$$ it is unreal. Their politics oozes into the rust project.
Can you elaborate on that?
You need some Iron. You're not you when you anemic. You're not oxidizing 😂
Welcome to coding and closed/open sourced projects in the twenty-first century, people without a personality inject their politics when they should be doing their jobs.
@@dmitriidemenev5258 if you know you know if you don’t you don’t.
In the case you know, nothing either of us will say will convince the other.
If you don’t know, then you should experience it yourself and formulate your own opinion. There is a reason rust community is mock, and openly.
@user-xf5ty9yk7z I can guarantee it's the latter. Happens all the time.
No can ever convince me to switch from C++ to Rust
No one can ever convince me to use C++.
I think that people who learn anything without any passion and just because their only interest is money, not going to learn Rust. They will give up on chapter 4 of The Rust Programming Language. There are easier ways to get the same salary in software.
This video was a good summary on the issue. And thank you for the sensible title for this video.
An article I saw about this urged to not be blind to the fact that although 3 of 4 exploits found are related to memory safety, only a very small fraction of the real worst cybersecurity exploits discovered had been related to memory safety. Either way I hope rust gets developed further.
I wanted to investigate the rusty shackleford programming language but there was some controversy a few months back, so I went with Zig and I think Go is another one I need to try out.
So just because there was some controversy, you avoided it?
Nuclear Gandhi comes to mind regarding memory bugs
That was a underflow bug in his agressiviness status, not memory corruption.
Rust also disables over/underflown checks in release builds, because those checks are super slow.
To add a small pedantic correction. Writing Go is certainly simpler than writing Rust, but it does not take less lines of code at all. Go is very easy to learn and write, but it's hella verbose when compared to functional or functional inspired languages, like Rust
Dude just called go verbose lol.
And even through rust is somewhat inspired in functional programming, it could not be far from it
Agreed. Go is verbose, while Rust is terse. Pick your poison.
@@user-db2uj9vc7sEither you're a liar, or you're someone who assigns their errors to underscores
@@zactron1997 Most reasonable comment I've read.
Memory bugs are just one of the many classes of security issues, yet they make up over 70% of CVEs
I don't like rust anymore.
I never liked it to begin with
i don't see how someone could've ever liked it
Watching this in the middle of my math class
Oh shucks, now Rust is glowing in the dark.
IT'S A TRAP!!!
This joke has multiple layers in multiple directions, ranging from psy-ops and built-in backdoors (which itself can be made into a joke about being gay) to definitely not gay for Astolfo and anime "slurs" that the resident twitter furry population has coined.
@@DeclanDSI The old security code was intentonally leaked.(For death star entry)
You might be joking, but that's actually true. Any new techniques and stuff the 3 letter people couldn't fit in C/C++ compilers, and now it's difficult to shove them in there without a good excuse, those are all in the Rust compiler. They even tell you this in the name - Rust. Not to mention the crate/npm like system, nah thanks.
NSA suggesting rust and denounce C... Thank you, I have +1 reason to stay with C and hate rust
Exactly staying with my C, asm, python pipeline.
Jokes on you that's what they planned on
The CDC recommends changing your socks at least once a day. Now you have one more reason to have stinky feet.
White House: Rust is memory-safe!
The infinite variable lifetime glitch:
I would think that most space systems would be written in Verilog or VHDL and then made into hardware or used on FPGAs, no? If you want robust, failsafe, memory-safe, anti-fragile, efficient, minimal, and fast systems, the best solution is hardware languages.
FPGAs don't work because the software is more complex. I'm sure some things would use an FPGA like PID controllers and the like
fpga supremacy
You can write memory safe code with C, is not really hard, what people complain about is that the compiler doesn't check it before producing the binary, with Rust you are forced, however there are external verification systems like Coq that can check if the C program is memory safe.
So this analysis really comes from someone who has little to no idea about programming languages.
Even if verification software is as good as the borrow checker (probably isn't), you're still wasting time on extra passes and testing that comes after compilation when you could just have the Rust compiler verify the code right away.
@@Abu_Shawarib you don't even know what you're talking about (obviously) stating shit like "probably". yea me too, I have no idea about C, rust, coq, and it fucking pisses me off that people just have this mindset of "oh, I know it all better, so it maybe has to be how I think it its, so I am not even going to bother to look into whatever the fuck you said"
not calling you out, but everyone who thinks this way, and I genuinely believe that this is a wrong mindset to have. be open. try new things.
and remember, everything in life is a skill issue. using C? skill issue. using rust? skill issue. shit talking other programming languages? skill issue.
(aint no way I actually just send this garbage piece of a random comment out into the vast wide world of web... )
Regardless it's not hard to implement best practices, like paying attention to any causea buffer overruns or allocated memory.
Otherwise it's like saying blueprints should be banned because you can draw up a building structure that's unsafe.
That's why you get people that know what they're doing.
My friend started using Rust then he became my girlfriend. Weird.
Can we call it Gust? Like every distro could shorthand be referred to as the latest disGust. Food for thought.
I feel like to government making up departments now.. cause never heard of most of these😂
They gotta give their slow cousins something to do bro, can't have them working normal people jobs.
What, haven't you heard about the SSD,the Sandwich Safety Department? Someone has to protect us from unsafe sandwiches
@@andregt4561 😂😂
@@rockytom5889 dang tax hungry nepo babies😭
The "no GC" requirement is wrong, demonstrably so, since Java (and a VM) has been used for decades for satellites and even interplanetary craft. It's also a bit of a non sequitur, as whether or not something is using GC is a matter of perspective; e.g., you've delegated a scripting language or DSL to run on a VM or embedded in C/C++.
White House says no more C, C++. Time to double down on my C studies
0:35
Man I understand the need for a concise video.
But I think the context of them having excluded all GC languages because they're doing space software is very important context.
If you don't control the memory yourself, they can write backdoors into your memory without you knowing. It's for the children please understand.
Somebody please think of the children!
You know Rust doesn't do any memory management, right? If you were talking about a garbage collected language like Go, C#, JS, Python, etc. you might have a point.
Bro you're just falling into the compiler backdoor theory
The idea of a self replicating self hiding compiler backdoor that's impossible to detect and injects itself into anything you compile.
Aka there's no damn point because there's nothing you can do at that point anyways
@@thegoldenatlas753 precisely why they'd be pushing this language. It's one thry COMPLETELY CONTROL
@@UNcommonSenseAUS it would've been in LLVM if they did.
Meaning C C++ and the rest are just as backdoored
How about thinking about the feasiblity of such things before being adamant about shit
Shadow stacks solved like 90% of the problems rust claims to solve whilst not forcing you to engage with a language only good enough for tiny projects.
Many memory safety vulnerabilities lead to logic errors, like privilege escalation or reading attacker-controlled files or something, not just instant RCEs of the type a shadow stack can prevent.
Rust isn't 'only good enough for tiny projects' lol - Firefox's rendering backend, half of Google's Fuchsia OS, the Deno JS runtime, there are some pretty big projects written in Rust. Huge companies like Microsoft, Google, Amazon, and now the US Govt are talking about doing even more, do you think they just haven't noticed it's useless?
Ring 0 debuggers can exploit everything. Instead of chasing this futile quest why not be open and transparent for a change?
Why Haskell not enforced?!
Allow your government to tell you what to do, 'Murica.
Outsourcing development to unskilled code monkeys is not the problem.
So, the NSA has backdoored the Rust compiler is what I'm getting from this.
11:23 you do not even need to have a text editor to run a hello world program in rust: cargo init . && cargo run
Foobar2000, my favorite chiptune player
Pretty sure this endorsement is the kiss of Death for Rust. Mafia knows what's up. Rust sleeps with the fishes.
That's how mafia works
Would be really cool to see an ANSI/ISO standard for rust.
You'll never see one because Rust is a research language being maliciously represented as a production language. Its designer wants to be able to add whatever new feature strikes his fancy whenever he wants, and to remove it whenever it turns out to have been a bad idea, whether it breaks your code or not. This is fine if it's explicitly a testbed for new ideas, but not if it's for writing serious software that people actually depend on. C, C++, Fortran, Pascal, Eiffel, all these languages have standards and guarantees that if they're going to deprecate a feature and later remove it, you'll have plenty of warning, often on the order of a decade or more. This means that once code becomes functionally complete and all known bugs have been fixed, you can leave it alone for years and it will keep working. Imagine writing an OS kernel in Rust. You'd write a driver for the PC speaker, whose specification has been static for decades, get all the bugs out, and then have to rewrite it every time the language spec changes and your code won't compile anymore. And the designer *likes* it this way.
Every Language is memory safe if you know what you're doing; and no Language is safe if you don't.
Yes, you can dig a hole with a spoon but a shovel is best. If rust can guarantee memory safety, why mess with non memory safe Languages.
@@yoshikagespeedwagon8025 Spoon might be safe to use, but shovel was made for actually digging holes
@@yoshikagespeedwagon8025 Rust *cannot* guarantee memory safety. There exist operations that are both necessary and inherently unsafe, which you would have to implement with an unsafe block in rust.
If you're giving up the entire point of rust, why bother with the overhead instead of just using C? Rust is awesome and the majority of software would be better off running on it, but only using rust is foolish.
Good, now try patching a memory vulnerability on code you didnt write
@@araarathisyomama787 ??? That's what I said.
Considering the CVE count and how many of them aren't exploitable I think this whole thing really has gone far enough.
The biggest risks are still inadvertently public functions. Not sending a magic packet to a webserver and getting root access.
That's a problem programming languages actually can help with but they simply aren't. Especially if you're accepting friction on the level of Rust.
The economy can speak louder than the white house. You gotta give incentives for things to be grabbed when there's other options. Rust is giving me COBOL vibes now. I have in the past mocked the "rust community" because of their overly.. You know.. More suspicious about anything the small G endorses (not joking). Maybe it's just slower for new languages to catch on? We tend to prioritize efficiency and time. I also have heard of memory issues even after compiling though but I haven't confirmed and not a programmer. For Rust to be more implemented with niche critical systems, maybe that makes more sense? Can anyone else give me more insight into understanding this?
Its still a forced conversion, theres no real reason to move your codebase to rust if you can just use modern c++.
you cant be talking if youre not a programmer dude.
Oh my HRT, this is so heckin gender affirming
LMAO
wait till a hello world program now cost them 1billion to write
please use dark reader man, you fcked my eyes in morning.
Get better eye balls please
Go outside in the morning. You’ll feel better getting sun in your eyes.
Still have no idea what you’re talking about but I’ll keep watching
ReWrite the Declaration of Independence
In Rust
*and add gay rights in it 😂
@@worldspam5682 hell yeah!
im coming from 2040 and we still using c in almost all embedded systems
Rust is great for the right usecases. It has an extremely steep learning curve compared to other languages to get up to speed in productivity, but for critical software it is absolutely recommended.
It is much much easier to write safe and maintainable code than C++ due to less verbose syntax, enforced memory safety and enforced error handling and matching patterns.
But you can absolutely write unstable and unsafe Rust (unwrap everywhere, unsafe blocks).
Rust should not be used everywhere though.
In essence: If a Rust pro and a C++ pro would write the same critical code, the Rust code will be more trustworthy.
Have they ever heard of the "Safe C" library? On top of that, modern C++ is fairly safe. Rust limits your creativity. It should be on the list of recommendations, but not be the only recognised language. For some other tasks, other languages are required. VHDL, HDL for FPGAS, Ladder Logic for PLCs, MOJO PYTHON for AI, C/C++ for embedded systems, Zig for overall convenience, portability and backward compatibility with older languages, ASM for critical blocks of library development for system driver development/embedded C, the list will grow. Then, not all projects will start rewriting their codebase because the government is doing their space and AI stuff in Rust. Think of Adobe and Autodesk. Probably the parliament/congress is finding avenues to spend money on contracts and tenders. The initiative will ultimately go nowhere. I'm not excited at all. I had a notion that only the Government of India has always been incompetent in all aspects of technology and even administration. No! I was wrong. America is no different. BTW, I prefer Rust after C. It's still easier than other high-level languages out there.
>implying "government space stuff" is real
@@rusi6219 true!
@@rusi6219 true.
you have no WOMB. you have no OVARIES
But we do have memory safe programs with minimal runtime.
>But we do have memory safe programs with minimal runtime.
_____________________oog__p#5?757220__#db___77__?4og_gggg_________________________075bpbbd_____________________
_____________________#__g__#?__777?4#0?77?db20bp____gpgog_7g_____________________dbbbb2bd__#_____________________
__________________ggd?___________7pggp__#77__g__#d2po_5ddp_7_____________________2bg__#7bbb2_____________________
________________dp??_7gd________gd777b___#?___?77dg7p7b_74___________________20bgpbbbd_____________________
____________p?205____#?7???_??_d?_____b__#_____2____77dbdbog__#4_________________bbbd77bp2_____________________
_____________#_gd__?__#__p__?_________0_____g?7__p___2_______7bd__b__7p_____________dbbbbp077p_____________________
_______g__#72b__#77g_p__?__________________#__d__gp0b27bpoo__d__?_77b___7_____________dbbg__#bbbbb_____________________
________#____#g__#_____#7o___________d___g0____72005ddp__?____?______57b______________7bpbbbbbb2_____________________
_____?__dg?_2_____74__________7_d_____?dbbbg#?____#?_______7__7b_____________0770bpbb2_____________________
____2____2____#____________________b7____2bd__??____#?______________779g_________bbbbbg20?_____________________
_____7__2_b7_________g________#?__70p__72____o?_____________________7o______dbbgd7bbdb_____________________
______bg?_?_____g0?_________#?____bod0pgdp#?__________________________7p____2dd5bbbbb2_____________________
_____g_d#?5___g#7?____#?7752___________77###__#b_________________________7b___20775bppb2_____________________
_____bdd___7_db?___p2o__#_____?77o7p_______________7bog______________________b_gbbbbdgd772_____________________
_____7b7__4_72___p2?____p_____02___________g000_7___7779og_______________7p2bbg__#7bbbbd_____________________
______b_d___db__d__#___5gp0__#o__#p__0p__________2000____________7__?g____________7dbdbbbbbbbd_____________________
______2d_bg?1_#?___5p00b2bg__#b__b7p____________?_____go?_________77g__________20bbbbbbbp?_____________________
______2__7b_g?___g2d777bg#?_2_?__2____pp0__________2dddbbbb4_____7g________dbpgggpd0b__#oo___________________
________#p__dp__?______7pdd#?___2?___2__d000?________7pgd0202000pg_____5________277bbbbbbbbbdb_________________
______?2_2d7________72?___g?7____7b_77____gpb_07722207__#7b_7p2__#7b____7_______g0pgggggggp__#?__________________
_______#_b___?7p7_______2___g?_________b77__g_20b20b020__#775__2__#7bbbd7g___________25b7777bd70___________________
____7__b7g0p52_____d?_g?___________7p__22g0b0002d__#9b__gd00bppbbbbd7p______7p_g02bbbbbbd__#___________________
____?__7__2bb_2__#og_gb__?______________7__22db02bd52___2p0000077?__#dpbbb7p_____7p__02__##__#00b____________________
_________7pb72p7g___b________________b_7b7d2d0bb79_g000b?_______72bpp7p_7___7p_2gbbbbbd?___________________
__________?b_?70db__b________________7p__7d20b77pp000?_7b_________bg7pdp_3___7_7bpbbdg?____________________
___________b_b__?7b_2_________________7___7dbb_5d000?____0________7p__#7ddp_b_700p7070g______________________
___________2_5__b__7db_________________5___73pd7700b_____db________bg7_27p7b7__#d0__?0b__#d7p____________________
___________7__b_b___70p_________________7__7?3pbbb7p_____db________bd2__27_7_ggdpdbbbb2____________________
______________7_7g____75p________________7____7pbbbb_____d?________bbb2?7b0_0_70bdbbbd__#____________________
______________d___b_____7p________________7o____5pbb_____2________gbbbg?7bdp_7_7dgpgp?_____________________
______________7___do#?72070_________________7p___7p2_____b_______d7bbd2?dbdg_7__7777b__#o____________________
____________p__#777_7____bbbbdbg_____________________7_____b______dbbgp0_70g__?##?_7020bd0__77o________________
________o?7?___________7bbbbbd7bg__________________7p____?_____d272?2o7g__#bp0__#__g27bbbd__?____7779g___________
_____p??_________________7bppbbdg05og_______________3_________d77577g__#7b7b2___?_7pb2pd#?__________77bg_______
___p?_______________________7027bbbbd77bpg_dg________7o_____p?_7777p7g7____?_2pbbbg?________________77o____
_g??__________________________77__#ggbbdg0bd77b0ppp_______72b277oo_7__?0pbb70_92bdb7bd?____________________77o_
p?________________________________7772bbbbbbb7d27bgg0_7g_?77boppp307pbbb70p20772?_________________________?
?_____________________________________7__#dgggpd0bbd7d770200ppdb20dp2p2g00b002bbg__?___________________________
___________________________________________77bdgpd0bbbbdbb7bbb2b75d7b5dbgb2gp#?____________________________
________________________________________________77bgpbbbd2ppbbdbpbbbbbbgp77?_______________________________
____________________________________________________77777?_77?##0?77777?___________________________________
@@MentalOutlawjust like modern C++ and C written with strict compiler flags
wha?
@@witokijaYWNBAW
I trust it less now.
You can take my MALOC from my cold dead hands
I'm kind of torn on this topic. I just started learning Rust a couple months ago because I wanted to do something different from C but I still want to work more on the lower level. I think its basically un-enforceable to make people write code in a certain language in general, but of course they could try, especially if it's government software.
Immediately when I see this kind of recommendation coming from the government, I think what they have to gain from it. Some people have brought up the idea of a backdoor in one of the languages they recommend (like Rust), but that seems pretty difficult given the language is open-source. And if one major open-source software is compromised, then following that logic none of them are safe. But that's not the discussion here.
My very naive prediction is that this isn't really gonna do much except maybe increase some Rust jobs. It's not like you can just stop writing things in C++ or C, especially since there is so much of that code which already exists.
Rust it too bloated I will stick with my tiny c99 compilers.
What about Ada programming language? It is used by the military.
Also I will add the fact that Rust will never replace C. EVER. People forget that the reason why C is so ubiquitous and hasn't been dethroned for what it does since it's inception 50 or so years ago. C is more or less high level assembly with all that comes with it.
I can only imagine how many schizos are on the Chans freaking out because the NSA recommended Rust. Now we're going to see Rust software re-written in C.
Don't have to look for them. They are on this very comment section.
/g/ is right about rust
ok Current Thing supporting Ukraine flag profile picture
@@jebediahkerman8245please re-read and correct your comment. It makes no sense
@@jebediahkerman8245 Ok "I'm against the current thing" chud.
Does anyone know the robot name at 7:10? Doing some research, thanks!
Screenshot and reverse image search. I ain't doing it.
So stay the he'll away from the fed boi approved software.
I'll never stop programming in Perl 5, and I'll program in K&R C till the day I die.
The thing is: you can totally write memory safe modern C++ and it's not even that hard.
just one more standard and sepples is good for real this time guys
@@miles2142 lol. just one more bro
I hate that basically all rust jobs are de-fi, I don't want to work with that regardless if it stays i just hate it
I used to like rust. But now I hate it. If the white house endorse something you know something must be wrong with it.
Rust backdoor confirmed
I got a quarter into the video before I realized they weren't talking about the game Rust created by Facepunch studios
Considering how often "Biden.exe" crashes due to memory leaks, I think it is safe to say, RUST was not the coding language used.
That’s why we need to rewrite him
From a president who slowly leaking his remaining memory a reminder to not leak memory.