On Sat, 1 Apr 2006, IOhannes m zmoelnig wrote:
in reality, the achieved latency is always to large - so workarounds have to be found to lower it. i am pretty sure that the 1st thing that would be thrown out, is anything that is not written in C.
If you start throwing out the slowest code first, start by throwing out Pd. It's slower than Python when it comes to interpreting the messagesystem.
Then if anyone has a use for a stdlib object that is too slow, let them provide a corresponding C object but which runs faster. In the case of things like file operations, the harddisk latency is so high that the presence of an interpreter doesn't make any notable difference on latency.
(note: Ruby has a garbage collector, which does cause a significant problem on latency. Python doesn't so it's ok)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada