Christian Seberino wrote:
Andrew Lentvorski wrote:
In order to replace Python, the next language I learn will have to
handle concurrency elegantly.
Why is concurrency important?
How about a responsive UI?
Why do I have to write my code so that I have to do a cooperative
preemption on long operations to give the UI some time? Why aren't the
UI and my computation (which have no interaction 99.999% of the time)
independent.
Then, if I *do* put the UI in an independent thread, then I have to do
bizarre things to schedule UI changes, updates, etc. because I'm in
thread 2 and the UI is in thread 1. Why aren't these things protected
and monitored *in the UI toolkit*?
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
