Exactly. Attention mechanisms excel at extracting signal from noise. This would simply reinforce that noise can come in this shape.
sleep_deprived
joined 3 months ago
This is worse than planned obsolescence. This is basically manufactured ewaste.
The last I heard, the issue is that the person that maintained the code left, so it's still on some super old version of PHP. So they need to upgrade the entire codebase to a modern version, which can be a very involved process. I could definitely be wrong though.
I'd really rather we skip over ARM and head straight for RISC V. ARM is a step in the right direction though.
I was skeptical of the Russian asset claims during the first Trump presidency, but after everything he's done this time around, it really seems like there's no other possibility.
Fun fact, Rust has a special error message for this:
Unicode character ';' (Greek Question Mark) looks like a semicolon, but it is not.
It also detects other potentially confusing Unicode characters, like the division slash which looks like /.
Tell me you don't know what a programming language is without telling me you don't know what a programming language is
I have this great idea for an app, we can go 70/30 on it! 70 for me because the idea is the hardest part after all. So basically it's Twitter plus Facebook plus Tinder with a built in MMO. You can get that done in a couple weeks, should be pretty easy right?
In simple terms, they just don't allow you to write code that would be unsafe in those ways. There are different ways of doing that, but it's difficult to explain to a layperson. For one example, though, we can talk about "out of bounds access".
Suppose you have a list of 10 numbers. In a memory unsafe language, you'd be able to tell the computer "set the 1 millionth number to be '50'". Simply put, this means you could modify data you're not supposed to be able to. In a safe language, the language might automatically check to make sure you're not trying to access something beyond the end of the list.
No, the industry consensus is actually that open source tends to be more secure. The reason C++ is a problem is that it's possible, and very easy, to write code that has exploitable bugs. The largest and most relevant type of bug it enables is what's known as a memory safety bug. Elsewhere in this thread I linked this:
https://www.chromium.org/Home/chromium-security/memory-safety/
Which says 70% of exploits in chrome were due to memory safety issues. That page also links to this article, if you want to learn more about what "memory safety" means from a layperson's perspective:
https://alexgaynor.net/2019/aug/12/introduction-to-memory-unsafety-for-vps-of-engineering/
view more: next ›
Oh, we've long outdone Chernobyl. Industrial pollution, oil spills, microplastics, regular plastics, PFAS, overfishing, habitat destruction... The modern ecological disaster caused by the US alone, before you even add in the rest of the planet, is so unfathomably large in scale that honestly it doesn't even warrant a comparison to Chernobyl.