To be fair same can't be said of ECC, even though ECC should be basic feature out of the box.
8,245 karma · joined March 28, 2012
Edit: Someone on Reddit compiled a list of various fuckups. https://www.reddit.com/r/browsers/comments/1j1pq7b/list_of_b...
And the Rust wasn't the root cause but corrupt configs were being erroneusly duplicated.
Arguably less bad than silently corrupting your data and forcing you to do CAPTCHA everywhere.
Which is what the parallel Perl(?) component was doing at the time.
Rust solution gave a clear signal something was wrong, the other solution was slowly annoying everyone and pushing them away.
Did you check if I name my project 朽木?
Supposedly even drowned their member that divulged their existence.
We don't have prior experiences that can tell us with certainty that LLMs will or will not replace humans entirely.
Projecting that LLMs will become a singularity is the same as saying processor's clock speed will double every year. They do double, they don't.
Sun will always rise in the east until it engulfs us.
No one can predict the future least of all humble extrapolation line.
Or at least you have to add memory safety as another extra step on your road to correct by design.
I'm aware of paths to memory safety, but they boil down to: pervasive GC, annoying compiler, and praying you got it right.
If you write your proof in GC language than translate it to C, that's just a mix of pervasive GC and praying.
It's a bit like saying, "Yeah, our system is safe, but if there are two threads racing or use after free somewhere, then all bets are off."
There is a lot to dislike about this paragraph:
It doesn’t matter that the language you use is memory-safe, if you didn’t design for correctness or have no process that will eventually lead you to fixing all bugs.
And no, asserts don't fix all bugs, they just guarantee some of your invariants are held at best, used in test at worst.
It's not just an ethical problem.
The strict definition being we don't count developments that happened before version 1.
Like when we talk about Rust, we don't mention the virtual threads or GC or the @ symbol for GC references. Even though those all happened during its development.
Seeing how US economy is K-shaped, the answer is the rich. Assuming of course the service is right.
It's easy to write code that trivially eats memory. Plus any resources spent on it, are resources not spent on other cloud provider things.
It leads to corruption. To paraphrase Dilbert "I'm going to code myself a car."
* terms and limits may apply.
Just switch to a saner language.
And before I get attacked for being a Rust shill, I meant Java :P
The bar is so low it's floating near the center of the Earth.
Pricing has no correlation with profit. It can be artificially lowered to kill competition, and artificially inflated to maximize profit.
As a straight guy, number of times people attacked Rust for catering to "that crowd", "DEI-language", and "woke mind-virus" has been pretty huge on Xitter.
Which is always hilarious to me, since language itself doesn't have anything offensive.
> If you write Rust, or let AI write rust, do you have to partake in the identity politics?
Answer is of course no. However by choosing to write it you'll be perceived as anti-Zig, anti-C, pro-woke, etc.
https://www.statista.com/statistics/203247/shares-of-househo...
But Rich also account for majority of consumed goods purchased.
Also why did Travel, Entertainment and Food services suffered during post COVID recovery?
Why are McDonald's and other fast food joints that upped their price enjoyed a surge in value, when supply and demand tells otherwise.