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?
Thread beginning with comment 474971
To view parent comment, click here.
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"
Delgarde
Member since:
2008-08-19

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

RE[2]: Comment by Mystilleef
by Mystilleef on Mon 30th May 2011 06:00 in reply to "RE: Comment by Mystilleef"
Mystilleef Member since:
2005-06-29

It's still a novel idea in the web arena. Async event-based programming has been the way to program desktops apps for about 2 decades. Web app development is still predominantly synchronous. Async event-based web frameworks are the exceptions, not the norm, in web programming. Remember Javascript only started being abused a few years ago with the hype that "Ajax" spurred.

Reply Parent Score: 2