@lbljeffmo @awbjs @stefanpenner what's an encapsulated public property?
@lbljeffmo @awbjs @stefanpenner there is a huge diff between code that created a variable accessing it and public properties.
-
-
@wycats 1/ Data is created per-inst. Logic is created per-class. Logic with access to non-this-inst data@awbjs@stefanpenner -
@wycats 2/ can still mess up in a non-local way. Logic with access to only this-inst data can only mess up@awbjs@stefanpenner -
@wycats 3/ locally (repeatedly locally given many insts sure, but narrowing the path from start to bug is smaller).@awbjs@stefanpenner -
@lbljeffmo@wycats@awbjs@stefanpenner Since dawn of Harmony, we've agreed on goal of class- not instance-private instance variables. -
@BrendanEich private class vars haven't shipped so it's still worth talking through@wycats@awbjs@stefanpenner -
@lbljeffmo@BrendanEich@awbjs@stefanpenner instance-only makes comparisons hard and custom constructors (Parent.withPerson()) annoying -
@lbljeffmo@BrendanEich@awbjs@stefanpenner lesson learned from Ruby :) -
@wycats@lbljeffmo@BrendanEich@stefanpenner same with Smalltalk. Instance private forces cluttering public API to support binary methods - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.