Is memory safety just a meme?
>>106541469~60% of all software vulnerabilities are caused by retards with a non-memory safe language
no but there are a lot of programs out there written in an, *AHEM*, memory-safe language that don't NEED such a thing.
>>106541517You just pulled that number out of your asshole, didn't you?
>>106541550perhaps :<it's kind of leaky. want to see it?
>>106541469yes
>>106541469Not really, but targeting memory safety makes the easy problems easier at the cost of making the hard problems harder. It's a terrible trade
It's not just a meme at all. It matters, but it's also not sufficient by itself.
>>106541469Idk try using windows 95s drivers for a month and get back to us
>>10654151799% of cybersecurity attacks don't involve interacting with the system itself but with the people using the system
>>10654151799.999% of vulnerabilities are caused by retards who forget to writeif (!logged_in) { return 403;}
if (!logged_in) { return 403;}
>>106541469It's not anti hacking shit feature you dumb fag
>>106541469>Is memory safety just a meme?It was solved in the 1960s by the invention of the Garbage Collector, which was required to solve the funarg problem in Lisp. Something only a really brilliant, genius mind could do: John McCarthy. As long as you don't blow up the heap, you're safe. If the heap is filled, the program freezes execution or terminates. Of course, programming is pop culture. First (1970s) the pop culture mantra was "lisp runs slow", then in 1980s Lisp was made to run blazing fast but "now GC bad, requires tons of memory". Then in the 1990s you had more memory and Java appeard, but again, pop culture said "Java slow". Then in the 2000s Java now runs fast but "GC bad because GC pauses". Subsequently we now have concurrent garbage collectors, thus not a problem anymore but now "GC bad".Memory safety was already solved down to the inner core of the operating system on Lisp Machines (1980s-90s), where even the operating system code used garbage collection. They dissappeared due to astronomically high prices and propietary software that remains propietary up to this very day.
>>106541469Not a meme, but way overrated.
>>106541706So many such cases.
>>106541550He did. The real number is around 70% as stated by Microsoft.
>>106541469'memory safety' in programming is like avoiding car crashes by giving everyone a tank filled with pillows, but never teaching driving.
>>106541469>IT sector bends over backwards to """protect users""">They open emails with a PDF for a "FREE $100 OFF COUPON CLAIM NOW" regardlessSociety is rotted to the core because actual THINKING skills aren't taught to people, no one at any stage of education is required to teach people how to not be scammed or even just the saying "if it sounds too good to be true, it probably isn't true"You can't idiot proof everything, its just not possible
>>106541517Some of the biggest software vulnerabilities are caused by that but majority is some webdev being a retard.
