Google's take on memory safety

H. S. Teoh hsteoh at qfbox.info
Wed Mar 6 19:13:26 UTC 2024


On Wed, Mar 06, 2024 at 06:51:47PM +0000, M. M. via Digitalmars-d wrote:
> On Wednesday, 6 March 2024 at 17:16:24 UTC, H. S. Teoh wrote:
> > On Wed, Mar 06, 2024 at 09:19:20AM +0000, RazvanN via Digitalmars-d
> > wrote:
[...]
> > Called it. Since years ago. It's been clear then, and becoming even
> > clearer now by the day, in today's landscape of bots that constantly
> > scan the net for systems with memory vulnerabilities, that the days
> > of memory-unsafe languages like C or C++ are numbered.  Software
> > systems have developed to the point that manually managing memory
> > just doesn't cut it anymore.  Systems have become too large, too
> > complex, and memory issues have become intractibly difficult to
> > handle manually.  It's time to let go of the illusion of total
> > control over one's memory usage and make use of real solutions.
> > Like the GC. ;-)  Or any of the various automated memory management
> > schemes.
[...]
> I wonder what Linus is thinking about all this bashing of C...

Linus, being Linus, probably doesn't care. :-D  Well, he'd probably
write a diatribe about why they're totally wrong, and then he'll just
ignore them and keep doing whatever he's doing.

None of that stops the inevitable, though.  Memory-unsafe languages are
on their way out. It may take another 20 years, or it may take 50 years,
but make no mistake, their demise will come. That much is sure.


T

-- 
Not all rumours are as misleading as this one.


More information about the Digitalmars-d mailing list