adr1an@programming.dev to Python@sh.itjust.worksEnglish · 3 months ago1 hour in Javapiefed.jeena.netimagemessage-square15fedilinkarrow-up170arrow-down16file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up164arrow-down1image1 hour in Javapiefed.jeena.netadr1an@programming.dev to Python@sh.itjust.worksEnglish · 3 months agomessage-square15fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squareTootSweet@lemmy.worldlinkfedilinkEnglisharrow-up7·3 months ago“Hardware cycles are cheap. Wetware cycles are expensive.” Paraphrased from something I once heard Jacob Kaplan-Moss say but don’t remember his exact wording at PyCon many moons ago.
minus-squaretaladar@sh.itjust.workslinkfedilinkarrow-up4·3 months agoThen why do Python people insist on having the programmer do so much stuff instead of letting a compiler do it?
minus-squaretaladar@sh.itjust.workslinkfedilinkarrow-up1arrow-down1·3 months agoVerifying that your different pieces of code actually work together. With a static type system and similar compiler features you can lighten the mental load a lot compared to languages like Python where you need to keep it all in your head.
“Hardware cycles are cheap. Wetware cycles are expensive.”
Then why do Python people insist on having the programmer do so much stuff instead of letting a compiler do it?
Examples?
Verifying that your different pieces of code actually work together. With a static type system and similar compiler features you can lighten the mental load a lot compared to languages like Python where you need to keep it all in your head.
Such as?