Timeline for If immutable objects are good, why do people keep creating mutable objects?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 9, 2014 at 21:51 | comment | added | Giorgio | I read this comment of mine after two and a half years, and my opinion has changed in favour of immutability. In my current project (which is in Python) we are using mutable objects very very seldom. Even our persistent data is immutable: we create new records as the result of some operations and delete old records when they are not needed any more, but we never update any record on disk. Needless to say, this has made our concurrent, multiuser application much easier to implement and maintain up to now. | |
Aug 24, 2012 at 15:48 | history | made wiki | Post Made Community Wiki by supercat | ||
Aug 17, 2012 at 16:19 | comment | added | Giorgio | +1: I agree: after learning some Scala and Haskell, I tend to use final in Java and const in C++ everywhere. I also use immutable objects if possible and, while mutable objects are still needed very often, it is amazing how often you can use immutable ones. | |
Jun 6, 2012 at 11:27 | history | edited | Gary | CC BY-SA 3.0 |
Grammar improvement
|
Jun 6, 2012 at 8:34 | history | edited | Florian Salihovic | CC BY-SA 3.0 |
Changed expression for better understanding.
|
Jun 6, 2012 at 8:33 | comment | added | Florian Salihovic | Yes, that's right. | |
Jun 6, 2012 at 8:32 | comment | added | Den | Perhaps "known" rather than "popular" would be a better choice of word. | |
Jun 6, 2012 at 7:55 | history | answered | Florian Salihovic | CC BY-SA 3.0 |