>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
>>107651149i was expecting something more complicated than that.all these workloads are trivial to parallelize because you can subdivide data along easily manageable linesasync/await can become complicated in c given that you have to deal with os internals thenfor something like that, yeah, id easily understand why one would want helpbut what you mentioned really isnt complicated. saying that it takes a genioos to deal with that is a lazy excuse for not gitting gud
>>107651180>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%I haven't been paying close attention to Swift development, but at least some of the bloat there is in trying to express intent to the compiler succinctly without having to tie yourself up in knots. Unfortunately, these compilers need a _lot_ of information about intent that C and C++ don't care about, so the language gets bloated and (especially in the Rust case) stuff looks ugly.
>>107651180>the usecase for c is to be basically a macro-asm. especially in tyotl 2025Then you've never used macro asm. C has nothing in common with assembly. C is a castrated high level language.>of 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.They spent billions of dollars on that and it doesn't work and went nowhere.
>>107651101eh you are confusing thingsthe rust compiler is a bit strict in how you signal what you are doing rather than C where its implicit so it avoids ambiguous s code when it comes to memory managementthread locks are easier to manage in rust because of this explicitness about memory (as concurrency is all about managing shared areas of memories between threads) but you can absolutely make the same mistakes as in C when it comes to it, because theres not really a way to guarantee itand you can have memory leaks in Rust because its innerent from a ref counting system vs garbage collection (its the tradeoff that is made)
>>107651213>saying that it takes a genioos to deal with that is a lazy excuse for not gitting gudI'm in favor of getting good, but even if I were to spend 10h a week on stuff that's not my webshit job or going to the gym so my body doesn't fall apart I wouldn't be good enough
>>107650069>Microsoft is hell-bent on eliminating Windows by 2030.ftfy
>>107651216like i said, you can derive everything you need to tell rust- from unmodified c codec++ is something else because youre supposed to use a layer of abstractionsso alot of the information becomes indeed implicit>>107651221>C has nothing in common with assembly.ok, your opinion is invalid then.im sorry but it is what it is. its trivial to anticipate how the key parts of your assembly will look like, from c code. the compiler then takes care of stuff like register pressure for youit IS a macro asm. asm, but with a huge chunk of it- automated away>>107651224>in C everything is implicitin the measure that youre not explicitly stating your intent with a specially designed syntax, yes.but all the information you might need is explicit. unless you work with compiled libraries. but then all bets are off because you then work with asm, not cand so i see no reason why i should be going out of my way to tell the compiler information it can derive from my code itselfthence: bad product. uncooked, unrefined
>>107651249i refuse to believe itit is 100% a matter of trainingi master this kind of shit bc i have 300klocs of c under my beltgranted, theres the pressures from the industryand other reasons why its not practyical for people to, for instance, write exclusively in c for one whole year, if not morebut thats another discussionthe point remains: it can be done, and its not a matter of innate qualities, but of training
>>107651296>it IS a macro asm. asm, but with a huge chunk of it- automated awayThat's called a compiler. Have you ever used an assembler?
>>107651321nope.and i kinda dont see how an assembler with macro functions is any different from a compiler, except for the fact its not the whole program that is written in "macros", only select parts of it
>>107650069>Using Rust is basically admitting that you are incapable of writing memory safe code without a crutch.Just like 99% of C developers who have plagued us with vulnerabilities for decades and still continue to! I love too how you're so obsessed with Rust that it's what you pulled from the headline and not the part about using AI to generate most of their codebase going forward.
>>107651367youre right, but you dont factor in the air of superiority rust evangelists are known forand volens nolens theyre the face of the whole language
>>107651385>youre right, but you dont factor in the air of superiority rust evangelists are known forIt's nothing compared to Ctrannies. The average Ctranny acts like he invented the computer.
>>107651547uhhhhh yeah no.the people who do c just because its considered a hard language are orders of magnitude less annoying than crabstheyre much more knowledgeable toorust is getting shilled by nocoders mostly, and because its an lgbt icon
>>107651385>>107651590>>107650750The overwhelming vast majority of Rust threads on /g/ are cniles crying about Rust or general shitposting against Rust. You people are literally mentally ill and obsessed with Rust. It legitimately lives rent free in your heads. Get help.
>>107650069Can jeets even write Rust?Rust is just such a pain to get working compared to everything else, including C/C++ that the only people I've seen using it are autistic white men and trannies. In the case of MS, it might acutally be a good thing. Rust based Windows/Office/Azure would filter out all those jeets and the software quality might actually improve.
>>107651604>another no-uok, i think ill ignore you because you seem to have a very low iqas expected from a rust evangelist
>>107651610Lmao, keep coping over your obsession
>>107651730cope with what?your mental retardation?thats quite literally a you problem...
>>107651604you're literally just making shit up, take your meds schizo
