Channels
#getting-started
- t
tejainece
06/03/2016, 9:08 PMwhy was this decision made? - t
tejainece
06/03/2016, 9:08 PMof not having fields? - t
tejainece
06/03/2016, 9:08 PMsounds very counter intuitive - t
tejainece
06/03/2016, 9:08 PMusually you build properties on top of fields - c
cedric
06/03/2016, 9:08 PMProperties are more powerful - r
Ruckus
06/03/2016, 9:09 PMThat's exactly what happend - r
Ruckus
06/03/2016, 9:09 PMThat is why Kotlin properties automatically have getters and setters in Java - t
tejainece
06/03/2016, 9:09 PMok. but why remove fields? - r
Ruckus
06/03/2016, 9:10 PMWhy not? - t
tejainece
06/03/2016, 9:11 PMbecause it is counter intuitive? - t
tejainece
06/03/2016, 9:11 PMfor people coming from every other language in the world? - t
tejainece
06/03/2016, 9:12 PMhaving to use
keywordfield - r
Ruckus
06/03/2016, 9:12 PMI don't think so. You treat it the exact same for the most part. - t
tejainece
06/03/2016, 9:12 PMinstead of the actually field - t
tejainece
06/03/2016, 9:12 PMnot giving access to that field outside the accessors - r
Ruckus
06/03/2016, 9:13 PMGenerally speaking that is considered bad design. In the case where you do need it, you can just use a private property.👍 1 - c
cedric
06/03/2016, 9:14 PM@tejainece: Do you understand the benefits of properties? - t
tejainece
06/03/2016, 9:14 PM@cedric: i do. - c
cedric
06/03/2016, 9:14 PMThey are a superset of fields: they serve the same purpose but with added functionalities - t
tejainece
06/03/2016, 9:15 PM@Ruckus: what is considered bad design? - c
cedric
06/03/2016, 9:15 PMexposing public fields👍 3 - t
toadzky
06/03/2016, 9:15 PMalso, it's not counter-intuitive to "every other language". c#, swift are just a couple that have had this for years - c
cedric
06/03/2016, 9:15 PMGroovy too (RIP 🧌)👍 5 - t
toadzky
06/03/2016, 9:15 PMit's not a JAVA thing, but it's definitely been a thing before now - f
fellshard
06/03/2016, 9:47 PM - f
fellshard
06/03/2016, 9:49 PMThe idea is that we ought to design our objects in such a way that there is no distinction in form between methods of nilarity and observing some state of an object, and methods of unarity and setting observable aspects of that object. - f
fellshard
06/03/2016, 9:50 PMIt's basically like providing controls on the outside of an object that both display state and optionally allow modification of that same state, like some sort of dial or lever. - f
fellshard
06/03/2016, 9:53 PMIt allows consistent expectations, and helps us build objects that represent their internal state in ways that are clearly and concisely expressed to outside observers. - t
tejainece
06/03/2016, 10:03 PMdoesnt say anywhere having fields is a bad design - t
tejainece
06/03/2016, 10:03 PMdoes it?