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

[Timon Gehr]

On 7/29/24 07:30, aberba wrote:
> 
> This back-and-forth about the action plan to move to @safe by default 
> (if it's even going to happen) isn't encouraging... I don't mind the 
> debates,

Well, this debate is not about default safety at all, it is not even 
about safety checks, it is about properly understanding the difference 
between `@system` and `@trusted`.

> but this doing seem to be yield a resolution.

Designing a good programming language is hard.

> Maybe you guys should meetup and hash things out.
> ...

That happens too.

> We the regular users are the ones supposed to be pushing back, not the 
> top contributors (core members??).

This sentiment is wild to me. There is no such separation. This is an 
open source project, with a lot of transparency. I think these public 
debates are actually a strength of D. People say what they think.

If you check out my track record with D, I do have some particularly 
high-profile contributions to the compiler, but a majority of the work I 
have spent on D is actually forum debates and bugzilla issues.

There are also contributors who are mostly silent here but do a lot of 
very important work on the compilers. Walter is both a prolific 
contributor to the compiler and a prolific debater on the forums. I 
think he is right about a lot of things, but clearly most communication 
is required when there are disagreements.