Ahhh, the sweet feeling of freedom. Today is my first day back at work (in person) in three weeks, and to celebrate, I’m going to a meet up tonight in Los Altos. Hey, you celebrate your way, I’ll celebrate mine :).
Seriously, though, I’m excited about tonight’s topic, and specifically from a testing perspective.
NOte: this entry is shifting into “Live Blog” mode now. That means please feel free to refresh if you want to get updates of what’s going on. If you see “End of Session”, you’ll know I’m done ;).
San Francisco & Silicon Valley Web performance Group
Large sites have made the decision to move their rendering back to their servers, and it not only has increased performance, but it’s also given better SEO and indexing to the sites as well. Progressive enhancement made sense once upon a time, and more and more people are coming back to that same idea.
After Page Load
jQuery 1 is about 90K unzipped. jQuery2 is roughly the same, YUI, and Dojo are similarly sized. Loading the libraries takes upa a lot of space. There are economies of scale that can be leveraged, but over time, the library code that is used vs what’s actually loaded becomes a very large delta. Over time, the Library grows. Component code that is performant and responsive, but expensive to develop, drops when the options are encapsulated in a library. The danger is that the Library coe, over time, become more prevalent, and loads up and takes up memory when most of the code will