<?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>Antanova Ltd. &#187; browser</title>
	<atom:link href="http://antanova.com/tags/browser/feed" rel="self" type="application/rss+xml" />
	<link>http://antanova.com</link>
	<description>We make excellent websites</description>
	<lastBuildDate>Tue, 30 Mar 2010 09:08:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google Chrome</title>
		<link>http://antanova.com/blog/web-development/google-chrome</link>
		<comments>http://antanova.com/blog/web-development/google-chrome#comments</comments>
		<pubDate>Thu, 04 Sep 2008 18:46:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Web-development]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2008/09/04/google-chrome/</guid>
		<description><![CDATA[As you will of course be aware, Google has released its new browser, Chrome. I’ve tried it out briefly, and everything seems hunky-dory. I think I’ll use it to access Google’s own apps. As for day-to-day browsing, I think I’ll stick with Firefox. After all, can I really trust Google not to harvest data relating [...]]]></description>
			<content:encoded><![CDATA[<p>As you will of course be aware, Google has released its new browser, <a href="http://www.google.com/chrome">Chrome</a>. I’ve tried it out briefly, and everything seems hunky-dory. I think I’ll use it to access Google’s own apps. As for day-to-day browsing, I think I’ll stick with <a href="http://www.mozilla.com/">Firefox</a>. After all, can I <em>really</em> trust Google not to harvest data relating to my web browsing? I don’t think so. Also, there’s no <a href="http://noscript.net/">No Script</a> available for it, without which it’s a bit difficult to block Google Analytics.</p>
<p>On the plus side, another browser is a good thing. It gives people another choice other than the dreadful Internet Explorers. Yes, and I mean IE7, too. Chrome uses the <a href="http://webkit.org/">Webkit</a> rendering engine, so there shouldn’t be any real surprises in rendering.</p>
<p>Let’s hope this comes out of beta soon, along with IE8 and we can start using some CSS3. How I long for that day.</p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/web-development/google-chrome/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A night at the Opera</title>
		<link>http://antanova.com/blog/web-development/a-night-at-the-opera</link>
		<comments>http://antanova.com/blog/web-development/a-night-at-the-opera#comments</comments>
		<pubDate>Sun, 27 Jan 2008 20:58:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Web-development]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2008/01/27/a-night-at-the-opera/</guid>
		<description><![CDATA[Firefox has become over the years an indispensable tool for me as a web developer. Firstly, its standards support for css is very good, even if the current stable release doesn’t pass the Acid2 test. The extensions that are available for it are both numerous and useful, none more so than the web developers’ toolbar.
Trouble [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mozilla.com/"><span class="blsp-spelling-error">Firefox</span></a> has become over the years an <span class="blsp-spelling-corrected">indispensable</span> tool for me as a web developer. Firstly, its standards support for <span class="blsp-spelling-error">css</span> is very good, even if the current stable release <span class="blsp-spelling-error">doesn</span>’t pass the <a href="http://www.webstandards.org/files/acid2/test.html">Acid2 test</a>. The extensions that are available for it are both numerous and useful, none more so than the web developers’ toolbar.</p>
<p>Trouble is, with all those <span class="blsp-spelling-corrected">extensions</span> loaded onto it, it becomes one heavy browser. That means that when I’m off duty and just surfing around, I notice things like the pause between clicking the “new tab” icon and being able to type anything in the address bat of the new tab that just opened.</p>
<p>Enter <a href="http://www.opera.com/">Opera</a>, a fast, light browser that until now had been on my machine just for testing. It’s <em>so</em> quick, sometimes I’<span class="blsp-spelling-error">ve</span> finished reading a page before I’<span class="blsp-spelling-error">ve</span> even clicked the link to visit it. And the back button is the fastest I’<span class="blsp-spelling-error">ve</span> ever seen. Javascript-wise, it’s very quick too, just a tad behind <a href="http://www.apple.com/safari/">Safari</a> in my experience. Most sites work fine with it, but sometimes I find I have to fire up Safari instead, <span class="blsp-spelling-corrected">although</span> that’s surprisingly rare considering its market share and my expectations.</p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/web-development/a-night-at-the-opera/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
