jotting down notes on different libraries

revisting backbone...
has promise
but I'm leaning more toward knockout at this point.

I know that backbone doesn't enforce any one way to manage data on the client side and how that data is tied to the DOM. I can see where that could be a benefit for some developers with a stronger preference for one way or another. I don't have much preference at this point, and I would be happy to have something existing manage that for me.,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8

keep coming back to python to javascript translators
but I think the real key is going to be to work natively with useful libraries created for DOM interaction.

reading up

on this page there is a nice description of the single threaded nature of javascript:

this snippet displays the latency on your browser for executing the next cycle:

var i = 0, diff = 0, d = new Date()

var timer = setTimeout(function() {
diff += new Date() - d
timer = setTimeout(arguments.callee, 0)
if (i++==1000) {
alert("Resolution: "+diff/i)
d = new Date()
}, 0)

The key to the above, and many timing issues in javascript is:
setTimeout(function_call, 0)

also some considerations for making sure that changes to the DOM are re-rendered before continuing to the next display update.,or.r_gc.r_pw.r_qf.&bvm=bv.41018144,d.aWc&biw=987&bih=887

looking at different python to javascript converters... looks promising...
just want something simple