Should You Use Immutable Objects?
Maximum Reliance on Immutable Objects Is Widely Accepted as a Sound Strategy for Creating Simple, Reliable Code. Immutable Objects Are Particularly Useful in...
Maximum reliance on immutable objects is widely accepted as a sound strategy for creating simple, reliable code. Immutable objects are particularly useful in concurrent applications. Since they cannot change state, they cannot be corrupted by thread interference or observed in an inconsistent state.
Are immutable objects better?
Immutable objects offer a number of advantages for building reliable applications. As we don't need to write defensive or protective code to keep application state consistent, our code can be simpler, more concise, and less error-prone than when we define mutable objects.
Must Read
What is the point of immutable objects?
Immutable objects are thread-safe so you will not have any synchronization issues. Immutable objects are good Map keys and Set elements, since these typically do not change once created. Immutability makes it easier to parallelize your program as there are no conflicts among objects.
James Sterling reports on renewable energy developments, climate policy, ecological conservation, and green tech innovations around the globe.
