luc.maison...@free.fr wrote: > The points above are not theoretical one. Vector3D was mutable and it > cost us weeks of works at that time to track difficult bugs in a > complex application. This was not a simple problem of communication: I > was involved in all teams from commons-math to high level application, > the rest of the team was just around me and we exchanged lots of > information. After we changed to immutable, all problems were gone and > we didn't notice any performance drawback. In fact, another team in > another project facing huge performances problems looked at what we > have done and changed also their objects to immutable: they got > significant performance improvements after that change because their > code was copying everything beforehand and it was not needed anymore > afterward.
+1 The cognitive overhead of dealing with the possibility of side effects is a serious brain drain, particularly on such a fundamental atom. Embrace immutability, and rejoice. -- Eric Bowman Boboco Ltd ebow...@boboco.ie http://www.boboco.ie/ebowman/pubkey.pgp +35318394189/+353872801532 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
