Is concurrency hard?

[Alex Arnon]

On 11/5/05, Robert Raschke <rrerlang@REDACTED> wrote:
[snip]

I get the impression a lot of people think about where and how to
> store data when programming (i.e., how do I manipulate the data),
> instead of concentrating on the transformational aspect (i.e., what am
> I doing to the data).
>
> I think that as long as you are concentrating on manually moving data
> about in piecemeal fashion, you are unlikely to notice any
> opportunities for making use of concurrency.
>
> I feel that the best way of noticing concurrency in your application
> is by carefully crafting the vocabulary that describes your problem
> and its solution. Very often you will find that storage does not rate
> very highly in such a vocabulary, allowing you to concentrate on the
> functional ascpect of you application. Even more fundamentally, if
> your vocabulary does end up with words for things that need storage,
> you can be sure that they are the ones that will limit your
> concurrency.


[/snip]

Thank you for so eloquently putting that into words, I've been trying to
properly verbalize this for a while :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20051106/3dc83103/attachment.htm>