.webp?h=8 "Cat Ears (wiggly) - MEOW MEOW MEOW MEOW MEOW MEOW MEOW")
threadThe CTO of Azure (microsoft garbage) considers C++ deprecated
Joining the club, along with Linus Torvalds. Cool stuff.
Who's gonna tell em? 
What the heck is up with the replies? It feels like the comment section of any Biden tweet except on the tech side - all the crazies come out.
I genuinely think Rust peeps should stay away from these threads. They're full of bad faith arguments, trolls and a lot of people with who you can't reason with in that format.
tfw Rust peeps can't come out of their shell
's refutation:
Every day for Rust I've seen this kind of thing. Every fricking day, and yet people still eat it up. I work in C++ a lot and honestly learned to enjoy it, and I really have little interest in abandoning it. Yes, some if not quite a lot parts of C++ are shit, but because I can accept that many things in life will always have shit, and jumping ship over something being shit only lands me in a different kind of shit. Consider any of my following opinions just 
Rust is, in my opinion, not the ULTIMATE solution, it still has logic errors, it still has panics, it still has issues, it still has int overflows, it also has poor, slow (to compile) implementations (and little documentation on those specifications too, we're all stuck with Clang 
), and I'm still a heckin valid conservative on the idea of Third-party package managers.
Despite making up 99% of the software ecosystem, Memory errors make up 60% of all critical vulnerabilities (or some such or whatever etc rust good c and c++ super bad!!)
You want to know the best point that never gets brought up when people say shit like this? It's always the root cause of these memory issues. You know how much fricking C++ code exists out there that's literally just C-style C++ and full of legacy pointers with very little testing? Holy fricking shit, I mean, a good chunk of bad C++ memory errors are just caused by gross, underlying C libraries and fumbling of real pointers. C++cels have had plenty of debugging cowtools for decades now, like Valgrind 
and hundreds of cowtools std::rangeing (
) from smart pointers, std::span, RAII, std::variant, even fricking vectors and std::array with basic fricking overflow detection
please note my opinion is on C++ as a hobbyist language, I'm not 100% talking about C++ for BIPOCs: as for corposhits go I think Rust is a good thing. If someone's gonna shit out code I'd prefer it being working, safe code, and not horribly written C++. But it still won't stop "runtime" bugs and incorrect logic, which is always the cause of those sepples memory issues in the first place.
Jump in the discussion.
No email address required.
As someone who has been coding C++ professionally for over a decade, your hobbyist opinion is 100% objectively correct. Literally everything you said is why I refuse to fall for the "Rust is gonna take over!" meme - it doesn't solve all the problems it claims to, it doesn't have a fraction of the ecosystem C++ does (especially in the embedded world), and modern C++ is a thousand times safer than old C/C++ if you know how to actually use the darn cowtools that exist.
Here's something fun for you: if you ever want to make Rustcels seethe, point out that thanks to the lack of a proper spec technically all Rust behavior is undefined behavior.
Jump in the discussion.
No email address required.
I've only been working in C++ for only 3-4 years now, and I've done incredibly stupid shit in C out of curiousity and easily learned that C has it's flaws despite what the neurodivergents defend it as (it is a good breather language from C++ when I get tired of writing it). I've peeped several languages and I don't 100% have anything against Rust besides the community being r-slurred. It really does have a terrible spec behind it but this is so i've only heard (and peeped) and barely has other real implementations besides it's LLVM rustc stuff, it was one of those languages that decided to roll out as you built the spec, which is just a horrible idea in it's own. But nah, everyone keeps consisting "X language is DEAD!!!" and "Y language is DEAD!!!"; languages don't die and it was never a competition, for fricks sake even Java has the advantage that you can build on one system and still run pretty fast code on others without recompilation (true portability issues aside) alongside it's generally simple language structure with not much to remember.
And yeah, some parts of modern C++ are shit but I think C++20 is really the final pat on the back to keep up with all the new languages. C++ is surprisingly under-credited and hated, but the only statistic I'll point out is simply: Look at all the years and time people have spent trusting C++ to be reliable and writing fast and efficient code in it without any gimmicks (... and pretend that Boost never existed, just like JQuery was to JS), even if Rust is truly better, C++ has just proven that it'll survive while still being a bloated piece of shit. I'll go out of my way to defend that even JavaScript has done an a-okay job at fixing old flaws in the language and keeping new features, and not going full bullshit like a react.JS language and just leaving that up to the library designers
I like C++ because it's truly just the cuckservative language that tries not to go full-in on being a new goylang that solely exists just for marketing, but because it has a community of people who work together and form ideas for the spec and doesn't try to go full minimalist with C while providing all the shit and cowtools the programmer will ever need right in front of them.
Jump in the discussion.
No email address required.
What are your thoughts on golang.
Jump in the discussion.
No email address required.
More options
Context
OUT!
Jump in the discussion.
No email address required.
More options
Context
More options
Context
More options
Context