Open GoogleCodeExporter opened 9 years ago
There already are a couple of optimizations that work well for applications
that predominately output text.
Applications that intersperse escape sequences with relatively short runs of
text are always going to suffer. This is mostly a result of the fact that DOM
operations are expensive in all current browsers.
If you have any ideas how to improve this situation, I'd be interested in
hearing about it.
For applications with long runs of text (i.e. for most applications other than
the one that you were looking at), the biggest cost is usually in the network
protocol.
Old-school HTML semantics unfortunately restrict the latency and bandwidth that
we can achieve. I have started work on WebSocket support, which should give
significant improvements for browsers that support them.
Unfortunately, other real-life responsibilities have prevented me from
completing this work. Give me a little more time.
Original comment by zod...@gmail.com
on 23 Jul 2010 at 12:39
Original issue reported on code.google.com by
superda...@gmail.com
on 23 Jul 2010 at 12:11