We want a single-crowned cccy tech

After reading _Java Concurrency in Practice_ by Goetz et al, I have come to think that current Java concurrency technology is double-crowned. One is thread safety, which is naturally convincing as a programming rule and care. Another is visibility, which is nothing but an issue borne by optimization artifacts from underlying low-level systems.

I think the visibility issue should be completely transparent to the user of high-level language. Programmers suffering and taking much care for such issue is felt quite unreasonable and counter-productive because they/we just want write code in a human-readable language which could be run as its natural, or common sense, semantics could assume.

[706 byte] By [hiwaa] at [2007-10-3 3:39:44]
# 1
If you don't care about performance then you need only deal with locks and can ignore any visibility issues. Real world programs need to push the performance envelope and they want atomics, lock-free data structures etc where visibility and ordering are crucial.
davidholmesa at 2007-7-14 21:35:14 > top of Java-index,Core,Core APIs...