This is post is entirely because I found some excellent text, directly from the W3, that sums up the issues I had with staying afloat in a competitive market (selling “skillz”) with a codebase that not so much changed as rotated every few months. I sympathise with anyone mad enough to create a Facebook app’…
A rather wordy but ultimately interesting look at Parallaxing images by Paul Lewis of HTML5 Rocks:
Whether or not you like parallaxing sites is one thing, but what you can say pretty confidently is that they’re a black hole of performance. The reason for this is that browsers tend to be optimized for the case where new content appears at the top or bottom of the screen when you scroll (depending on your scroll direction) and, in general terms, the browsers work best when very little changes visually during a scroll. For a parallax site that’s rarely the case since many times large visual elements all over the page change, causing the browser to do a repaint of the whole page.
His conclusion don’t guess, test is obvious; but thankfully he also provides methods to put this idiom to practice!
H5R’s responsiveness was much better on my BlackBerry Curve (OS7) than my Dual-Core portable running Firefox 17; but looking at the article and what it tries to achieve I think that’s no surprise. The amount of code that’s pulled from syndication alone is eye-watering, thankfully it’s all very pretty!
- Unlike Facebook, Famo.us thinks HTML5 rocks. Here is why. (gigaom.com)
- Scrolling Performance (html5rocks.com)
Responsive web-design came about largely due to changing demands of the equally modern web-user.
For example: as it’s more and more likely that this given person will like and be able to view images through their browser (no matter the device they’re using); what happens if you wish to use the same set of images through all screen-sizes? It turns out, just add some CSS:
The Marcotte-related fun doesn’t stop there… Read More…