* the only viable approach? v8 is pretty fast; in my programs, i've seen firefox being faster only once yet (in an optimal case for tracing)

* LuaJIT is a tracing JIT

* what are massive performance improvements? i'd say the jump from pure interpreter to static/tracing JIT compilation has already been a massive performance improvement

so no daily commute?

no, you can't. you see the just the silhouette of the code, not the while code itself - because when selected, tabs and multiple spaces rougly look the same.

aren't whitespace, brainfuck* and ook! the same languages (just differently named keywords)?

please, think of james bond! how could he drink a martini gracefully when a suitcase is chained to his hand?

james gracefully holds cocktail glass with both hands? now if he had other hand around woman's waist, that I would understand :)

i tried csscaffold, but ran into nothing special yet. despite a minor bug it just worked. the biggest nuisance is that my ide (currently netbeans) reports lots of errors in the scaffolded css file because of course it's not valid css anymore.

i like the domo kun.

while i belief in machine consciousness, i don't think human-like intelligence - as described in popular science fiction culture - is likely (though not impossible). intelligence: yes. superhuman intelligence: yes. but human-like intelligence, as in "thinks like a human, reasons like a human"; no * . the bodies, senses, cultures, etc would be just too different.

so silicon-based intelligence would be very strange and incomprehensible for us, and i doubt we'd recognize it as an intelligent being easily.

* with the possible exception of eliza

chrome definitley wins. but i think, (tracemonkeys) tracing could be THE feature in this case. lots of unrolled loops ... hopefully mozilla gets more out of it over time.

17 chrome tabs@1ms ~95%