ZILtoid1991@lemmy.world to Programmer Humor@programming.devEnglish · 1 year agoFunctional bros be likelemmy.worldimagemessage-square55fedilinkarrow-up1313arrow-down117
arrow-up1296arrow-down1imageFunctional bros be likelemmy.worldZILtoid1991@lemmy.world to Programmer Humor@programming.devEnglish · 1 year agomessage-square55fedilink
minus-squarejkrtn@lemmy.mllinkfedilinkarrow-up9·1 year agoI think using both is normal. Closures and objects are duals of each other. Do whatever is understandable and maintainable, neither paradigm is magic.
minus-squareKogasa@programming.devlinkfedilinkarrow-up1arrow-down2·1 year agoIs the duality statement meant to be true in a technical sense?
minus-squarejkrtn@lemmy.mllinkfedilinkarrow-up1·1 year agoYeah! For example, if the language allows closures to capture state, they can act like properties on an instance.
minus-squarejendrik@discuss.tchncs.delinkfedilinkarrow-up1·1 year agoA closure is a function with captured state. An object is state with methods.
I think using both is normal. Closures and objects are duals of each other. Do whatever is understandable and maintainable, neither paradigm is magic.
deleted by creator
Is the duality statement meant to be true in a technical sense?
Yeah! For example, if the language allows closures to capture state, they can act like properties on an instance.
I don’t see the duality
A closure is a function with captured state. An object is state with methods.