Quotes About Brian Goetz

Locking can guarantee both visibility and atomicity; volatile variables can only guarantee visibility.

immutability is not equivalent to simply declaring all fields of an object final. An object whose fields are all final may still be mutable, since final fields can hold references to mutable objects.

Yet accessing a volatile variable performs no locking and so cannot cause the executing thread to block, making volatile variables a lighter-weight synchronization mechanism than synchronized.[5]

When designing thread-safe classes, good object-oriented techniques—encapsulation, immutability, and clear specification of invariants—are your best friends.

The most common type of race condition is check-then-act, where a potentially stale observation is used to make a decision on what to do next. [4]

Static synchronized methods use the Class object for the lock.)

you can think of a ThreadLocal as holding a Map that stores the thread-specific values, though this is not how it is actually implemented. The thread-specific values are stored in the Thread object itself; when the thread terminates, the thread-specific values can be garbage collected. If