devilish666@lemmy.world to Programmer Humor · 2 months agoYup...i can confirm thatlemmy.worldimagemessage-square43fedilinkarrow-up1282arrow-down155
arrow-up1227arrow-down1imageYup...i can confirm thatlemmy.worlddevilish666@lemmy.world to Programmer Humor · 2 months agomessage-square43fedilink
minus-squarecbazerolinkfedilinkarrow-up22·2 months agoDynamic typing, special and unique syntax for every language feature, interpreter intrinsics
minus-squarerhabarba@feddit.orglinkfedilinkarrow-up16·2 months agoDynamic typing is the source of very amazing errors, see JavaScript.
minus-squaresuslinkfedilinkarrow-up9·2 months agoI think the problems there are exacerbated a lot by over-eager type coercion and other crappy design decisions inherited from almost 30 years ago
minus-squarebarsoap@lemm.eelinkfedilinkarrow-up5·2 months agoYep lua and lisp/scheme are also unityped and not even close to as broken. All are remarkably similar languages, theory-wise. …also something something Guido not getting tail call elimination and people sending him copies of the wizard book. It’s been a while. (And, yes, lua does proper tail calls).
minus-squareBrahvim Bhaktvatsal@lemmy.kde.sociallinkfedilinkisiZuluarrow-up5·2 months ago[object Object] !Reddit moment.!<
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up8arrow-down1·2 months agoOperator overloads, descriptor protocol, decorators
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up7·2 months agoOperator overloads are excellent for readable code when used well - I object to their inclusion on this list.
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up5·2 months agoAs long as you don’t have to implement it yourself.
minus-squareTheHarpyEagle@pawb.sociallinkfedilinkarrow-up3·2 months agoHonestly, I’ve been using type hints very heavily since they became a thing. I just use IDE completion too much to do without them.
Dynamic typing, special and unique syntax for every language feature, interpreter intrinsics
Dynamic typing is the source of very amazing errors, see JavaScript.
I think the problems there are exacerbated a lot by over-eager type coercion and other crappy design decisions inherited from almost 30 years ago
Yep lua and lisp/scheme are also unityped and not even close to as broken. All are remarkably similar languages, theory-wise.
…also something something Guido not getting tail call elimination and people sending him copies of the wizard book. It’s been a while.
(And, yes, lua does proper tail calls).
[object Object]Operator overloads, descriptor protocol, decorators
Operator overloads are excellent for readable code when used well - I object to their inclusion on this list.
As long as you don’t have to implement it yourself.
Honestly, I’ve been using type hints very heavily since they became a thing. I just use IDE completion too much to do without them.