Linked by David Adams on Mon 3rd Jan 2011 04:44 UTC
Permalink for comment 455976
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-07-08
It is a case of "Worse is Better".
The architecture requirements that you need to have to build a thread safe UI, provide minimal gains when compared to an UI which is single threaded and makes use of communication mechanisms between threads.
Having a multiple threaded UI, means you need to take care of:
- Who is holding which rendering context
- What threads are making use of which UI elements
- Which thread processes which UI event
- Race conditions to UI changes
- and so on
Having the UI event based and one thread responsible for drawing it, simplifies things a lot.