[whatwg] Application defined "locks"
robert at ocallahan.org
Wed Sep 9 19:53:58 PDT 2009
On Thu, Sep 10, 2009 at 1:33 PM, Jeremy Orlow <jorlow at chromium.org> wrote:
> In general this seems like a pretty interesting idea. It definitely would
> be nice to completely abstract away all concepts of concurrency from web
> developers, but some of our solutions thus far (message passing, async
> interfaces, etc) have not been terribly appreciated by developers either.
You have to be careful with developer feedback. Developers inexperienced
with pthread-style threads-and-locks typically like the model, since it's a
simple abstraction that *superficially* appears to map easily onto their
existing sequential code (e.g. because they can carry on using lots of
shared state). It's not until you get more experienced with it in a large
system that you really feel the pain, and appreciate why an apparently more
restrictive model might work better.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg