Yup...i can confirm thatdevilish666@lemmy.world to Programmer Humor@programming.dev – 213 points – 5 days ago42Post a CommentPreviewYou are viewing a single commentView all commentsDynamic typing, special and unique syntax for every language feature, interpreter intrinsicsDynamic 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 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).[object Object] !Reddit moment.!< Operator overloads, descriptor protocol, decoratorsOperator 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.
Dynamic typing, special and unique syntax for every language feature, interpreter intrinsicsDynamic 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 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).[object Object] !Reddit moment.!< Operator overloads, descriptor protocol, decoratorsOperator 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.
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 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).[object Object] !Reddit moment.!<
I think the problems there are exacerbated a lot by over-eager type coercion and other crappy design decisions inherited from almost 30 years 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).
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).
Operator overloads, descriptor protocol, decoratorsOperator 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.
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.
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.