Java Memory Model Pragmatics
shipilev.net
Java Memory Model Pragmatics
1–10 of 22 posts
Re: Java Memory Model Pragmatics
#2Just an FYI - 'select over' doesn't work on iOS Safari.
Re: Java Memory Model Pragmatics
#3This is very technical, most likely way past what 99% of developers both need to care about and have to care about.
Given that most developers work at best with embarrassingly parallel problems they wouldn't need to know much of these details.
But if you're up for it: It's a very rewarding feeling when you're both allowed to figure these things out and someone are also paying you while you figure it out.
Re: Java Memory Model Pragmatics
#4Just an FYI - 'select over' doesn't work on iOS Safari.
Copy and paste to notes was my work around.
Re: Java Memory Model Pragmatics
#5This is very technical, most likely way past what 99% of developers both need to care about and have to care about. Given that most developers work at best with embarrassingly parallel problems they wouldn't need to know much of these details. But if you're up for it: It's a very rewarding feeling when you're both allowed to figure these things out and someone are also paying you while you figure it out.
Who cares about "most developers". This is interesting for its own sake.
Re: Java Memory Model Pragmatics
#6In the section about nasal demons, did anyone else think the right answer was 12 too? I figured the parens make the context local so the ++ had to occur after the add.
Re: Java Memory Model Pragmatics
#7The memory model seems to be the real achilles heel for concurrency in Java. In the end with a only little bit of work one can master the concurrency primitives and they are quite usable. However understanding the full ramifications of the memory model is pretty much beyond mere mortals. As a result it is hard to do anything else than stick to established patterns and / or toolkits and frameworks if you don't want to set yourself up for insidious issues that are nearly impossible to reproduce.
Re: Java Memory Model Pragmatics
#8The memory model seems to be the real achilles heel for concurrency in Java. In the end with a only little bit of work one can master the concurrency primitives and they are quite usable. However understanding the full ramifications of the memory model is pretty much beyond mere mortals. As a result it is hard to do anything else than stick to established patterns and / or toolkits and frameworks if you don't want to…
> The memory model seems to be the real achilles heel for concurrency in Java.
I'd expand it beyond Java to shared-everything models in general. Any language with a shared-everything model is going to incur all this complexity. At least Java goes through this pain to ensure memory safety in the presence of unsynchronized accesses from multiple threads.
Re: Java Memory Model Pragmatics
#9In the section about nasal demons, did anyone else think the right answer was 12 too? I figured the parens make the context local so the ++ had to occur after the add.
There is no right answer to that problem.
Re: Java Memory Model Pragmatics
#10Was the English version of this talk recorded? I found the talk in Russian[1], but with my understanding of the Russian language, it's impossible to watch.