[Not really OT] Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language.

[Richard (Rikki) Andrew Cattermole]

On 22/07/2024 5:31 AM, aberba wrote:
> On Saturday, 20 July 2024 at 05:58:19 UTC, Richard (Rikki) Andrew 
> Cattermole wrote:
>>
>> On 20/07/2024 11:33 AM, H. S. Teoh wrote:
>>> On Fri, Jul 19, 2024 at 10:49:23PM +0000, mw via Digitalmars-d wrote:
>>>> [...]
>>> [...]
>>>
>>> It's 2024, and a NULL pointer brought down half the world's servers.
>>>
>>> Just gives you *so* much confidence in technology. :-D
>>>
>>> //
>>>
>>> In other news, this is yet another nail in the coffin of memory-unsafe
>>> languages. We're slowly, but surely inching towards the day when the
>>> likes of C and C++ will finally be relegated to the dustbin of
>>> history...
>>>
>>>
>>> T
>>
>> It is not if, but when will D be banned from being used in critical or 
>> long standing applications.
> 
> Can't critical applications be written with @safe turned on? How does D 
> fall short in that regard?

That covers non-lifetime, non-segfault, and non-assert issues.

Unfortunately you cannot rely on using things like signal handlers to 
throw an exception, as you may not own the thread let alone the process 
to have one.

Asserts/boundchecks/null deref these things cannot bring down the process.

This includes for web services too.

Imagine trying to explain to somebody that they lost 100k in sales 
because the web server they were connected to segfaulted out because it 
was written in D and not in an application VM language like Java. It 
would go down very well!