Timeline for If immutable objects are good, why do people keep creating mutable objects?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2013 at 20:53 | comment | added | Darrell Teague | This is probably a big point ... "because that is how everyone else is doing it" ... so it must be right. For a "Hello World" program it is probably easiest. Managing object state-changes via a slew of mutable properties... that is a little more tricky than the depths of "Hello World" understanding. 20 years later I am very much surprised that the pinnacle of 20th century programming is to write getX and setX methods (how tedious) over every attribute of an object with no structure whatsoever. It is only one step away from directly accessing public properties with 100% mutability. | |
| Aug 24, 2012 at 15:48 | history | made wiki | Post Made Community Wiki by supercat | ||
| Jun 7, 2012 at 12:12 | comment | added | Jaap | +1, the getter/setter pattern is used way too often as some sort of default implementation after the first data analysis. | |
| Jun 6, 2012 at 19:21 | history | answered | Jerry Coffin | CC BY-SA 3.0 |