.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.
"Learned to enjoy it," in the same sense that women can "learn to love" a psychopath who keeps them chained to his basement wall for 18 months.
I'm not an advocate for Rust, (as a general principle, I don't like any form of technology which is produced by a coercive cult which announces that it will now be taking over the world and everyone will use it whether they want to or not) but exactly the same thing happened with C++. Legions of vicious, elitist buttholes poured out of academia and mocked and denigrated anyone who resisted C++, and everyone eventually used it as a result. It had absolutely nothing to do with the actual merit of the language whatsoever.
I've realised, that more than anything else, programmers are absolutely spineless cucks. Most of you do exclusively what someone else tells you, and that means that the industry ends up defaulting to one absolutely degenerate pile of garbage masquerading as a programming language, after another. The worst thing is that it isn't always management who bullies you into using the latest piece of crap. It's normally another programmer; someone who you could actually get away with giving the punch in the mouth that they both need and deserve.
Jump in the discussion.
No email address required.
settle down buddy its not that deep
Jump in the discussion.
No email address required.
More options
Context
More options
Context