<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Optimization results</title>
	<atom:link href="http://www.schonhose.nl/2009/09/10/optimization-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schonhose.nl/2009/09/10/optimization-results/</link>
	<description>Bits of blogging and ranting by Schonhose</description>
	<lastBuildDate>Thu, 05 May 2011 18:40:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dennis</title>
		<link>http://www.schonhose.nl/2009/09/10/optimization-results/comment-page-1/#comment-14166</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Fri, 11 Sep 2009 06:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.schonhose.nl/?p=392#comment-14166</guid>
		<description>Using the scrollbar from the browser is indeed the simplest and fastest way to handle this. With the use of Flickr and other sites using this solution has become more or less mainstream. Pages build back in the late nineties (leave out the animated gif) are probably also a lot faster compared to the current pages.

But fast is relative, the speed in those days was also much lower compared to the current day internet connection. While this isn&#039;t a reason to make slow pages using a lot of overhead of several JS frameworks, I do feel we could add to the experience.

For example, the photoblog layout, written in late 2007, early 2008 uses several JS frameworks and additional single JS files. At the time this was the only way we could accomplish what we wanted. I did some research and found that almost 95% of all the features can be handled by JQuery, thus limiting the load. I&#039;m now in the process of porting my code to the JQuery framework and I tend to make a comparison on the load and speed of the page.</description>
		<content:encoded><![CDATA[<p>Using the scrollbar from the browser is indeed the simplest and fastest way to handle this. With the use of Flickr and other sites using this solution has become more or less mainstream. Pages build back in the late nineties (leave out the animated gif) are probably also a lot faster compared to the current pages.</p>
<p>But fast is relative, the speed in those days was also much lower compared to the current day internet connection. While this isn&#8217;t a reason to make slow pages using a lot of overhead of several JS frameworks, I do feel we could add to the experience.</p>
<p>For example, the photoblog layout, written in late 2007, early 2008 uses several JS frameworks and additional single JS files. At the time this was the only way we could accomplish what we wanted. I did some research and found that almost 95% of all the features can be handled by JQuery, thus limiting the load. I&#8217;m now in the process of porting my code to the JQuery framework and I tend to make a comparison on the load and speed of the page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Williams</title>
		<link>http://www.schonhose.nl/2009/09/10/optimization-results/comment-page-1/#comment-14162</link>
		<dc:creator>Jay Williams</dc:creator>
		<pubDate>Thu, 10 Sep 2009 22:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.schonhose.nl/?p=392#comment-14162</guid>
		<description>Have you thought about going super simple, and removing the fancy scroller, and going with the browser&#039;s horizontal scroll bar? That way it wouldn&#039;t require as much JS overhead, and you could go as slow or fast as you wanted.</description>
		<content:encoded><![CDATA[<p>Have you thought about going super simple, and removing the fancy scroller, and going with the browser&#8217;s horizontal scroll bar? That way it wouldn&#8217;t require as much JS overhead, and you could go as slow or fast as you wanted.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

