Like A Duck@programming.dev to Programmer Humor@programming.dev · 1 year agofinally there is a perfect monitor for Java programmerslemmy.mlimagemessage-square120fedilinkarrow-up11.24Karrow-down114
arrow-up11.23Karrow-down1imagefinally there is a perfect monitor for Java programmerslemmy.mlLike A Duck@programming.dev to Programmer Humor@programming.dev · 1 year agomessage-square120fedilink
minus-squarefredthedeadhead@lemmy.worldlinkfedilinkEnglisharrow-up3·edit-21 year agoKotlin would represent the getter/setters as synthetic properties (and do so automatically, since Kotlin interops with Java). object1.A = object2.X.Y.Z.I.J.K.E.getF(i).G.toString() Of course it’s still not great (there’s still too much nesting, there’s something fundamentally wrong with how the data is structured) but at least the code is less noisy.
Kotlin would represent the getter/setters as synthetic properties (and do so automatically, since Kotlin interops with Java).
Of course it’s still not great (there’s still too much nesting, there’s something fundamentally wrong with how the data is structured) but at least the code is less noisy.