> I’d be curious to know what kind of professional would choose to express themselves in this way, it’s pretty embarrassing. Embarrassing for pointing out that

> I’d be curious to know what kind of professional would choose to express themselves in this way, it’s pretty embarrassing. Embarrassing for pointing out that OO is dead and it is not acceptable to ask users to wait almost 40 years to get networking support into the standard library? No, C++ standard committee members should be embarrassed, not those disappointed users. > that blog post - as many Rust-themed blogs from start-ups - is a submarine article attempting to increase the notoriety of their product. As any article published by an commercial entity, it is always about increasing its economic benefits. Personally, I don't know anyone from the company but their blog is just one more success story of depreciating C++ and I applaud for that. > Having memory leaks in 2021 is incomprehensible. This is an amateur mistake of the worst kind in modern C++. Sorry but I stopped reading after this. I've been writing software for the past 20 years, worked for the biggest names in industrial, had my PhD in CS about 15 years ago, I write code on almost daily basis (Linux kernel modules, database kernel, infrastructure kind of code). I make the above mentioned amateur mistakes pretty often. Not saying I am highly skilled, just saying if I can make such mistakes after working 20 years in the field, it wouldn't be rare for other people especially those young developers. btw, I recently had a nasty memory leak bug in golang that took me a couple days to reproduce and debug, yes, in a GC based language.