>Microsoft plans to eliminate every line of C and C++ from the company by 2030.>Microsoft plans to translate the largest C and C++ systems to Rust.The rise of Rust and the downward trend of code quality are directly correlated. As populations become less intelligent, they rely more on the crutches built by previous generations. Using Rust is basically admitting that you are incapable of writing memory safe code without a crutch.
>>107650069one glimpse at the evolution of their workforce tells everything one needs to know...
>>107650069They’re using AI to translate into Rust, and AI can’t write Rust
If your enemy is making a mistake do not interfere.
>>107650069>downward trend of code qualitywhat code
>>107650237The start menu is now a web app that spikes the CPU, kek. This will only get worse.
>>107650234+1the picture of the combination of AI + jeet "engineer" writing millions of rust LoC is hilarious.>t. rustacean
>>107650237
>>107650249that's microjeet code. i.e. completely irrelevant. so is the intelligence of the populations of jeets, micro or otherwise.if you are a jeetsoft consoomer, you're even lower than microjeets in the intelligence ladder.
>>107650069I write C++ and Rust basically all day at work and in both AI will regularly shit out code that doesn't even compile. I'd say it's generally far better at Rust but I wouldn't want to rely on anything it's producing right now.
>>107650263'saved
>>107650255I bet Microsoft will use AI to do the heavy lifting with the Rust coding and have the Actual Indians audit the code where the debuggers list the bugs
>>107650657glorious meme material incoming, theni cant wait
>>107650069Why do C programmers complain so much about Rust but not any other language like Java or JavaScript? What's bad about Rust not depending on C that makes C programmers hate Rust but not more popular languages that depend on C?
>>107650730everybody complains about both java and javascript lol
>>107650730constant rust shilling + rust shills being unsorted garbagepython gets hate too. and its not dependent on, its literally written in c.
If it has Rust, it isn't good, simple as.
>>107650069The likes of NVIDIA and Rust becoming key components of Agenda 2030 was not on my bingo sheet, but I should have seen it coming.
>>107650730Rust is a C competitor. Java and especially JavaScript are not C competitors.
>>107651016no, rust and c have completely different usecasesrust is a competitor to c++
>>107650069This is gonna make rust look bad
>>107650069>The rise of Rust and the downward trend of code quality are directly correlated.Coincidence. I run a bunch of random well-written Rust utilities (although I'm not deeply looking into these authors' Mastodon profiles). One can write good code in Rust. Microsoft just isn't shipping good code anymore in _any_ language, at least not at scale.>Using Rust is basically admitting that you are incapable of writing memory safe code without a crutch.I can't write performant multithreaded code that doesn't fuck up without significant guardrails, and I'm not embarrassed to say so. AFAICT, only a tiny handful of people can do this, and we want more performant multithreaded code than a tiny handful of supergeniuses can provide.
>>107651042good. its uncooked. its a bad producttheres no justification for the borrow checker.you can derive all the guarantees of rust from c code, minus thread lockswe had a discussion about this around a week ago
>>107651029Not quite.One would write an OS in C, at least some parts.One would also write an OS in Rust, at least some of the same parts.So they're competitors (and not just Rust and C++), at least some of the time.
>>107651101>minus thread locksThread locks are important!
>>107651096>performant multithreaded codelike?
>>107651115https://github.com/sharkdp/diskus> diskus is a very simple program that computes the total size of the current directory. It is a parallelized version of du -sh. On my 8-core laptop, it is about ten times faster than du with a cold disk cache and more than three times faster with a warm disk cache.Also:you don't want your web browser's renderer to be limited to only one core, and you don't want it to be vulnerable to memory corruption bugs because that's how people get ownedyou don't want your PDF renderer to be limited to only one core, and you don't want it to be vulnerable to memory corruption bugs because that's how people get ownedyou don't want your video player to be limited to only one core, and you don't want it to be vulnerable to memory corruption bugs because that's how people get owned
>>107651105theyre not competitors. or c would be a competitor to java because you can write backends in it toothe usecase for c is to be basically a macro-asm. especially in tyotl 2025the usecase for rust is at a higher level. same level as c++. a sort of macro-c>>107651113of course. its just that its THE ONE THING not covered by an AST like system for which one could derive all the needed information from c-like syntax.so instead of learning the bloat that is rust, the rust devs could have used a c-like syntax and graft onto it a system to verify thread locks, cutting the bloat by 95%this is why i say its uncooked. im fairly certain even i could do bettermy solution is a change of frame of reference and grouping code based on the data it operates on, into timelines, instead of functions and code blocks. alot of things become dead easy to derive theneven thread locks, but im not 100% sure about that. i didnt really invest much thought into that
