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

Paulo Pinto pjmlp at progtools.org
Sat Jul 27 09:40:03 UTC 2024


On Friday, 26 July 2024 at 22:26:03 UTC, Don Allen wrote:
> On Friday, 26 July 2024 at 08:57:42 UTC, aberba wrote:
>> On Thursday, 25 July 2024 at 20:18:27 UTC, Serg Gini wrote:
>>> On Thursday, 25 July 2024 at 12:24:27 UTC, Paolo Invernizzi 
>>> wrote:
>>>
>>>> Nvidia manager, curious about what programming language we 
>>>> are using in DeepGlance as I claimed we care for memory 
>>>> safety.
>>>
>>> I bet core tech (eye tracking and object detection) is C++ 
>>> code :)
>>
>> I honestly don't get why D after 20yrs is being dragged (by a 
>> vocal minority) to become like rust. Shouldn't they be using 
>> rust already? A lot of very important new code is still being 
>> written in C++ (irrespective of its flaws). It's not like you 
>> can't write strict safe code in D either. Devs aren't stupid, 
>> it doesn't matter if strict is turned on by default or not at 
>> this point. They know what to do. There's way too many 
>> existing code in D to be dragging our feet with rust which is 
>> still niche by the way.
>
> I could not agree more. Trying to glue Rust-like features onto 
> this language really feels like ill-considered imitation, not a 
> good look for a language that has already been accused of 
> jumping on bandwagons. It also does not make technical sense to 
> me. I've written comparable amounts of Rust and D and for 
> ordinary applications without real-time constraints, I much 
> prefer D, so I don't have to become an involuntary part of 
> Rust's complex approach to memory management. Saying equivalent 
> things in D is so much easier easier than in Rust. But the more 
> baroque D becomes, the harder it will be for newcomers to find 
> the subset of the language that works for them.

In that regard, C# with the low level improvements introduced and 
improved upon since C# 7 (currently C# 12), alongside Native AOT, 
already did that for me.

Similarly, Java with Panama and Graal native image, Swift, Go 
(even if I avoid it as much as possible), and Kotlin/Native keeps 
improving.

This is what I was looking forward back when I got "The D 
Programming Language" book, instead,   the ecosystems listed 
above either catched up in missing features where D had an edge, 
or sprung to the existence, creating much bigger ecosystems, 
while safety keeps being discussed on the forums, GC or not GC, 
and so on the eternal discussion.



More information about the Digitalmars-d mailing list