Linked by Hadrien Grasland on Fri 27th May 2011 11:34 UTC
General Development After having an interesting discussion with Brendan on the topic of deadlocks in threaded and asynchronous event handling systems (see the comments on this blog post), I just had something to ask to the developers on OSnews: could you live without blocking API calls? Could you work with APIs where lengthy tasks like writing to a file, sending a signal, doing network I/O, etc is done in a nonblocking fashion, with only callbacks as a mechanism to return results and notify your software when an operation is done?
Permalink for comment 474971
To read all comments associated with this story, please click here.
RE: Comment by Mystilleef
by Delgarde on Sun 29th May 2011 21:45 UTC in reply to "Comment by Mystilleef"
Member since:

However, I know many developers (usually with a background in web development) who hate callback based programming. They claim it's hard to understand.

Like Lennie said, that's a weird thing to say. Web developers, of all people, are most accustomed to dealing with async behaviour. Javascript is a fundamentally single-threaded event-driven language, and it's been Javascript developers (via frameworks like Node.js) that have been pushing the async model into server side code in recent years...

Reply Parent Score: 2