On Fri, Dec 12, 2008 at 6:02 PM, Michael Dale dale@ucsc.edu wrote:
I am aware of the Yslow thread, is that what your referring to? .. it seemed to end with not much resolution or people mentioning its not much of a problem given the current javscript library set... and it seemed to assume that we would lose debug functionality...
Just wanted to mention it again since I think it will be a problem shortly and that the solution should be thought about.
For example it would be nice if all javascript libraries defined in a common way the set of messages they use so that user-language message text could parse that and package the localized language messages into the request. That way you don't have to issue separate ajax requests for language messages and you only send out the text messages for the associative interface components of the JavaScript libraries that your interacting with.
anyway as mentioned earlier I will try to experiment with a solution soonish. (if no one is working on this already)
Well: combining+gzipping alone is a really significant chunk of the total possible improvement and does no grave harm to debugability. Mostly improvement can come from minimising server round trips the size of the data transmitted isn't important except in so far as smaller sizes can reduce round trips to an extent.
Also, a less aggressive line number preserving minimization would be less harmful for debugability.
The prospect of a magic jsdebug option was raised in the prior thread, but I believe it was shot at because it doesn't help for rare problems and less-technical bug victims, people with stale cached copies of the JS (that flipping on debugging would avoid), etc.
Making ajax requests for message text would be pretty miserable performance wise.