Concurrency Quote by Brian Goetz

The combination of threads, remote-procedure-call interfaces, and heavyweight object-oriented design is especially dangerous... if you are ever invited onto a project that is supposed…

— Eric S. Raymond

“Accessing shared, mutable data requires using synchronization; one way to avoid this requirement is to not share. If data is only accessed from a…

— Brian Goetz

“Making all the components highly reliable will not necessarily make the system safe.”

— Nancy G. Leveson

“Immutable objects are simple. They can only be in one state, which is carefully controlled by the constructor. One of the most difficult elements…

— Brian Goetz

Safety is not a retrofit; it's been in our DNA since day one.

— David Baszucki

“The only way to make me stand in line for half an hour to buy a spool of thread, or to make me spend…

— Rose Wilder Lane

A multithreaded file system is only a performance hack.

— Andrew S. Tanenbaum

“There is no design so good that it can't be messed up by bad implementation.”

— Sravani Saha Nakhro

“Safety is a system property, not a component property, and must be controlled at the system level, not the component level.”

— Nancy G. Leveson

“withstand many wash/dry cycles (for more about blocking, see Chapter 7).”

— Amy Wright

“What would be the point of safety measures? What’s the point of a man balancing on a wire if there’s no risk of his…

— Mark Capell

“Safety is an illusion and perhaps it's better to challenge it sometimes, to see how far we can go, to learn about the stuff…

— Tania Aebi