<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Vesica Blog &#187; browsers</title>
	<atom:link href="/blog/tag/browsers/feed/" rel="self" type="application/rss+xml" />
	<link>https://vesica.ws/blog</link>
	<description>- Taking museum and art collections to the cloud</description>
	<lastBuildDate>Fri, 05 Jul 2013 05:25:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>In the game of browsers, Chrome Wins @ Vesica</title>
		<link>https://vesica.ws/blog/2011/06/in-the-game-of-browsers-chrome-wins/</link>
		<comments>https://vesica.ws/blog/2011/06/in-the-game-of-browsers-chrome-wins/#comments</comments>
		<pubDate>Sun, 05 Jun 2011 21:38:55 +0000</pubDate>
		<dc:creator>Asif N</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Using Vesica]]></category>
		<category><![CDATA[art collection software]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[compatibility]]></category>
		<category><![CDATA[firefix]]></category>
		<category><![CDATA[IE9]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[saas]]></category>

		<guid isPermaLink="false">https://vesica.ws/blog/?p=223</guid>
		<description><![CDATA[Over the last few days we&#8217;ve released several updates to the platform, with the result that we&#8217;ve been testing vigorously across all the latest browsers. Whilst Vesica works in Firefox 3.5 and 4, Opera 10+, IE 8 and 9, Safari 5 and Chrome 11 along with most tablet PC browsers, Chrome reigns supreme (at least [...]]]></description>
			<content:encoded><![CDATA[<p>Over the last few days we&#8217;ve released several updates to the platform, with the result that we&#8217;ve been testing vigorously across all the latest browsers. Whilst Vesica works in Firefox 3.5 and 4, Opera 10+, IE 8 and 9, Safari 5 and Chrome 11 along with most tablet PC browsers, Chrome reigns supreme (at least on Microsoft Windows).</p>
<p>I&#8217;m not going to go into details of performance, because the difference is really quite obvious without having to measure seconds and milliseconds. Here&#8217;s a brief run down of why Chrome really is superior browser:</p>
<ul>
<li><strong>Pages just load faster.</strong> Doesn&#8217;t matter whether they are heavy on JavaScript or HTML 5. In Chrome they load faster than in any other browser.</li>
<li><strong>No JavaScript Lag. </strong>I really had high hopes for IE 9 and Firefox 4 here, and whilst they perform vastly better than their predecessors, they simply do not do as well as Chrome does. For instance, the Vesica piece editing interface uses multiple JavaScript / JQuery tabs and accordions with multiple dialogs &#8211; compared to Chrome, all the browsers  will have some lag. Even if it is not very noticeable in FF 4 and Safari unless you specifically compare with Chrome, it is there.</li>
<li><strong>Smoother Animation.</strong> Again, this may have a thing or 2 to do with JavaScript loading better, but all JQuery and HTML5 animation is far better and smoother on screen with Chrome than it is with any other browser.</li>
</ul>
<p>Whilst I had high hopes for IE9 and Firefox4, I was a little disappointed. Although IE9 really does have great standards compliance and some FF plugins are virtually unparalleled, Chrome just delivers a far more superior experience for an application like Vesica.</p>
]]></content:encoded>
			<wfw:commentRss>https://vesica.ws/blog/2011/06/in-the-game-of-browsers-chrome-wins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
