1,468 karma · joined April 5, 2025
This article comes just in time to silence the heretics who ask what the use of an Optimus is. Promise a factory robot, deliver a Tamagotchi.
We have arrived at a stage where pseudoscience is enough to convince investors. This is different from 2000, where the tech existed but its growth was overstated.
Tesla could announce a fully-self-flying space car with an Alcubierre drive by 2027 and people would upvote it on X and buy shares.
The post you reply to does not indicate a misunderstanding of memory safety at all. .
The Rust literature is poorly written compared to C and Ada and the argumentation style on forums is sloppy, aggressive, and often unintelligible.
Which is a pity, because the language itself does not seem to be so bad.
"We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android’s C and C++ code."
Which means they had a pretty poor code base. If they had spent more time on engineering and less time on features that are canceled after 12 months anyway, they could have written better C/C++.
The Morris worm already worked without human intervention. This is Script Kiddies using Script Kiddie tools. Notice how proud they are in the article that the big bad Chinese are using their toolz.
EDIT: Yeah Misanthropic, go for -4 again you cheap propagandists.
But that is unlikely to happen. They'll be used for crowd control (which works because they look intimidating) and surveillance. Perhaps they'll also supervise humans that scrub the kitchen floor. Most likely they'll fail entirely.
https://www.schneier.com/blog/archives/2025/06/what-llms-kno...
At some point they'll monetize these dossiers.
Other objections like requiring 130 packages for a cryptographic application and inflated binary sizes are not mentioned.
https://blog.adacore.com/memory-safety-in-rust
Notice that in-bounds indexing is included, same as in the definition from this submission that I quoted at you.
I refuted that point by pointing out that the same process, if done manually in C++, would not be considered "static analysis that provides memory safety for array access".
"Memory safety—the property that makes software devoid of weaknesses such as buffer overflows, double-frees, and similar issues—has been a popular topic in software communities over the past decade"
And the buffer overflows are not detected statically except for the cases when the compiler can prove them. And Rust proponents keep ignoring the topic of this subthread, which is memory safety by static analysis.
https://www.reuters.com/business/media-telecom/cantor-nears-...
Masayoshi Son is BFF with Trump and Lutnick:
https://asia.nikkei.com/politics/international-relations/how...
There is more going on here than is publicly known. Investing in hot air is of course a specialty of the Trump admin.
So viewing their recommendations with caution seems wise.
Static analysis has a specific meaning, and rote insertion of bounds checking isn't it.
fn f(n : usize) -> usize {
if n == 0 {
10
} else if n % 32327 == 0 {
1
}
else {
f(n-1)
}
}
fn main() {
let a = [1,2,3,4,5];
let n = f(12312);
println!("{:?}", a[n]);
}https://stackoverflow.com/questions/28389371/why-does-rust-c...
For arrays, this problem is not computable at compile time, hence the sarcastic remark that, IF THE ABOVE DEFINITION IS TAKEN AT FACE VALUE, Rust must have solved the halting problem. Downvoters are so dumb here.