Linked by Eugenia Loli on Sun 13th May 2007 00:35 UTC, submitted by Luis
Permalink for comment 239746
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-01-02
I really don't understand how people can think that polling is ever the right solution. It's one of the first things you learn when studying low-power circuitry: asynchronous circuits generally save power. The same thing applies to software. Asynchronous, event-based programming keeps the machine quiescent when nothing is happening.
I think this is one of the few penalties of the distributed method of software development. There is no core set of practices and ideas on how to solve problems that are produced by interactions up and down the entire stack. And the loose-coupling of components often means that the event one desires to wait for is not exposed by the interface for the underlying component.