Smaller variables to have less going down the line? Sounds like striking out the pitcher to me.
One of my constant struggles has been where to build HTML that has to be built on the fly, server or client? On the server, lots more bytes to ship down the line but less javascript to run once it gets there. On the client, 10% as much data to send, but then lots of javascript to run to assemble the HTML. Anyone else ever struggle with this problem?
I don't know what that reference means, but welcome to web app optimization.
There are a couple of apps that can convert any HTML into their dynamic counterparts. You can also do some XML/XSLT/XHTML stuff, or you can load and pre-cache in the background, which might be your best bet. Depends on your architecture and what you are trying to accomplish. I've used all of the above. I'm sure there are lots more options.
Sorry. In major league baseball, the pitcher is often a terrible hitter, easy to strike out. "Striking out the pitcher" means doing the easy thing that almost anyone can do instead of focusing on the real problem (in the baseball analogy: striking out the good hitters).
One of my constant struggles has been where to build HTML that has to be built on the fly, server or client? On the server, lots more bytes to ship down the line but less javascript to run once it gets there. On the client, 10% as much data to send, but then lots of javascript to run to assemble the HTML. Anyone else ever struggle with this problem?