using locks means you are working with shared mutable state, which is
already bad up front.

if you want a concrete example, try wrap up a simple message queue system
in erlang and c++/java/..., compare the amout of work.  while erlang
has a good concurrency runtime, its immutable restrictions still helps
in making a good design.

basically, I believe "anything that can go wrong will go wrong".  one can
forget to lock but cannot modify immutables limited by language.

【 在 muser (负尽千重罪，练就不死心) 的大作中提到: 】
: 有什么具体事例支持这个说法吗？
--
FROM 180.173.114.*