Evolution of C
Evolution of C
If there was a simpler way to make C memory-safe, it would have been done decades ago.
We’ve had compiler sanitizers and valgrind for ages.
About how an Excel spreadsheet with no formulas stacks up against a corporate accounting suite. Valgrind is how you find the bleeding once you inevitably introduce a memory bug. I don’t understand all the fsanitize options, but I’m guessing they aren’t a blanket solution, exactly because memory bugs have still been inevitable.
This thread is making me wonder how many people actually understand what Rust does. It rigorously prevents any form of memory error at all in normal code, and unsafe blocks, where needed, tend to be tiny. It makes C segmentation faults look just as goofy as JavaScript type errors.
Wasn’t that the Loki show, where all of time is run by a boring dystopian corporate bureaucracy?
Now that I think of it, I guess you’re right, that show probably did do better than Black Adam.
There’s a lot of logos with hidden stuff like that.
Amazon’s logo has an arrow going from A to Z, implying they sell everything “from A to Z”
The Tostitos logo has two people holding chips (the Ts) and a bowl of salsa (the dot on the I):
Toyota’s logo has every letter of the company name in it:
The LG logo has the letters L and G in it:
The US is probably a much bigger market. I imagine it’s the same reason LG is English alphabet and not Hangul. Same with Kia, Hyundai, Samsung, etc.
But this is mere speculation. I could be 100% wrong, happens daily!