every day photos

https://vimeo.com/108551893 - 16 years, related http://jk-keller.com/daily-photo/related-photo-projects/


http://www.365plrds.com/slideshow.html


https://www.youtube.com/watch?v=tWzPDNabdBs

https://www.youtube.com/watch?v=3MPyoAN4FIk

https://www.youtube.com/watch?v=qJutZCyXEJg

https://www.youtube.com/watch?v=qJutZCyXEJg

https://www.youtube.com/watch?v=JSzL-osslUg

https://www.youtube.com/watch?v=9_Fms1Yyanc

https://www.youtube.com/watch?v=nN_jcom8TR4

https://www.youtube.com/watch?v=NQxyfOpZmAQ

https://www.youtube.com/watch?v=ZGgd0DUKok4

https://vimeo.com/99392

https://vimeo.com/125593599

https://vimeo.com/47134932
https://www.youtube.com/watch?v=VVe92OXwJpk
https://www.youtube.com/watch?v=OxT4HaE-ZdM
https://www.youtube.com/watch?v=e5sgWG2saxs
https://www.youtube.com/watch?v=Ertu9_MhFiM
https://www.youtube.com/watch?v=HWBqTyUfPlk

Double checked lock (DCL)

http://www.javaworld.com/article/2074979/java-concurrency/double-checked-locking--clever--but-broken.html

DCL relies on an unsynchronized use of the resource field. That appears to be harmless, but it is not. To see why, imagine that thread A is inside the synchronized block, executing the statement resource = new Resource(); while thread B is just entering getResource(). Consider the effect on memory of this initialization. Memory for the new Resource object will be allocated; the constructor for Resource will be called, initializing the member fields of the new object; and the field resource of SomeClass will be assigned a reference to the newly created object.

However, since thread B is not executing inside a synchronized block, it may see these memory operations in a different order than the one thread A executes. It could be the case that B sees these events in the following order (and the compiler is also free to reorder the instructions like this): allocate memory, assign reference to resource, call constructor. Suppose thread B comes along after the memory has been allocated and the resource field is set, but before the constructor is called. It sees that resource is not null, skips the synchronized block, and returns a reference to a partially constructed Resource! Needless to say, the result is neither expected nor desired.