@devilish666@lemmy.world to Programmer Humor@programming.dev • 3 months agoYup...i can confirm thatlemmy.worldimagemessage-square43fedilinkarrow-up1278arrow-down154
arrow-up1224arrow-down1imageYup...i can confirm thatlemmy.world@devilish666@lemmy.world to Programmer Humor@programming.dev • 3 months agomessage-square43fedilink
minus-squarerhabarbalinkfedilink16•3 months agoDynamic typing is the source of very amazing errors, see JavaScript.
minus-square@sus@programming.devlinkfedilink9•3 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-square@barsoap@lemm.eelinkfedilink5•3 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).
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]