<?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>impl.emented&#187; Firefox</title>
	<atom:link href="http://impl.emented.com/tag/firefox/feed/" rel="self" type="application/rss+xml" />
	<link>http://impl.emented.com</link>
	<description>— tracking the Web</description>
	<lastBuildDate>Fri, 02 Apr 2010 09:12:57 +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>Chrome Pushes for a Standards Based Web - a Challenge to Silverlight and Flash [Best of Sept. &#039;08 #1]</title>
		<link>http://impl.emented.com/2008/09/10/chrome-pushes-for-a-standards-based-web-a-challenge-to-silverlight-and-flash/</link>
		<comments>http://impl.emented.com/2008/09/10/chrome-pushes-for-a-standards-based-web-a-challenge-to-silverlight-and-flash/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 20:29:20 +0000</pubDate>
		<dc:creator>Jonas Bolinder</dc:creator>
				<category><![CDATA[Chrome]]></category>
		<category><![CDATA[Highlights]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[vision]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://impl.emented.com/?p=51</guid>
		<description><![CDATA[Chrome pushes for JavaScript and HTML 5. The JavaScript performance of Chrome vs. TraceMonkey. Chrome doing well on the Acid3 test. Chrome as a replacement for the operating system?]]></description>
			<content:encoded><![CDATA[<p>This week was all about <a href="http://impl.emented.com/2008/09/02/chrome-googles-first-steps-towards-an-operating-system/">Chrome</a>, the new fast and minimalistic browser from Google. I now use <a href="http://impl.emented.com/2008/09/10/google-chrome-tips-reducing-high-disk-and-cpu-activity/">Chrome as my default browser</a>, not bad for a 0.2 version.</p>
<ul>
<li> There was some discussion this week about which products and technologies are really <a href="http://www.theregister.co.uk/2008/09/04/chrome_review/">threatened by Google Chrome</a>. I agree with those who argue that other rich Internet application frameworks (RIAs) are the technologies at greatest risk. These include the proprietary <a href="http://news.cnet.com/8301-1001_3-10034365-92.html">Microsoft Silverlight</a> and Adobe Air (with Flash). The <a href="http://ostatic.com/172399-blog/chrome-javascript-and-flash-two-mostly-opposing-views">great promise of the Chrome browser</a> is that it pushes for the open technologies JavaScript and HTML. Chrome comes with a fast JavaScript engine, and with improvements in the JavaScript language itself, as envisioned by the recent <a href="http://impl.emented.com/2008/08/18/ecmascript-harmony-unifies-the-efforts-towards-javascript-20/">ECMAScript Harmony agreement</a>, JavaScript could become a real challenge to the programming languages used in Silverlight (C#) and Flash (ActionScript). ActionScript and JavaScript have the same roots in ECMAScript, but ActionsScript requires a proprietary runtime component (Air or Flash player) to run in the browser, whereas support for JavaScript is built-in into most browsers. Silverlight also requires a proprietary runtime component.
<p>JavaScript can not alone pose a threat to Silverlight or Flash, an enhanced HTML is required, with elements from the emerging <a href="http://www.w3.org/html/wg/html5/">HTML 5 standard</a>, such as the canvas element, for drawing to the screen, and the video element, for displaying video. The <a href="http://en.wikipedia.org/wiki/Canvas_(HTML_element)">canvas element</a> is currently supported by WebKit, the HTML rendering component used in Chrome, and by Gecko, the one used in Firefox, but not natively in IE, though there are workarounds. The latest Firefox 3.1 alpha 2 release includes support for the <a href="http://arstechnica.com/news.ars/post/20080905-first-look-firefox-3-1-alpha-2-officially-released.html">video element</a>.</p>
<p>Another advantage with Chrome is that it comes included with the <a href="http://gears.google.com/">browser extension Gears</a>, which is a JavaScript framework that equips the browser with additional capabilities like offline access for supported sites.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/chrome/">Chrome</a>, <a rel="tag" href="http://impl.emented.com/tag/javascript/">JavaScript</a></span></li>
<li> Last week I posed a question regarding the relative performance of <a href="http://impl.emented.com/2008/09/02/google-in-the-limelight-with-chrome-and-android/">Chrome's JavaScript engine V8 compared to the latest Firefox engine TraceMonkey</a>. Now John Resig has given a <a href="http://ejohn.org/blog/javascript-performance-rundown/">balanced answer</a>, and it turns out that V8 and TraceMonkey are quite comparable. V8 is faster in some tests, in particular those involving recursion, while TraceMonkey is faster in some other tests. For tests including both JavaScript and DOM manipulation, WebKit based browsers like Safari and Chrome are somewhat ahead of TraceMonkey and Firefox 3.0.1. IE is generally lagging behind.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/chrome/">Chrome</a>, <a rel="tag" href="http://impl.emented.com/tag/firefox/">Firefox</a></span></li>
<li> A proof that Chrome is relatively compliant with emerging Web standards is that it <a href="http://news.cnet.com/8301-13515_3-10030962-26.html">performs well on the Acid3 test</a>, with a score of about 78 out of 100.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/chrome/">Chrome</a>, <a rel="tag" href="http://impl.emented.com/tag/web-standards/">web standards</a></span></li>
<li> Finally, Ted Dziuba <a href="http://teddziuba.com/2008/09/a-web-os-are-you-dense.html">challenges</a> my <a href="http://impl.emented.com/2008/09/02/chrome-googles-first-steps-towards-an-operating-system/">comparison of Chrome to an operating system</a> last week, though he probably didn't read my article, instead he mainly goes after a post by Michael Arrington who <a href="http://www.techcrunch.com/2008/09/01/meet-chrome-googles-windows-killer/">labels Chrome</a> "a full on desktop operating system that will compete head on with Windows." Though that expression might be somewhat over the top, I enjoy the vision in the post that eventually the need for a stand-alone desktop operating system will disappear, and that basic OS features might as well be integrated into the browser. A possible solution could be based on a stripped-down version of the Linux OS combined with Google Chrome.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/chrome/">Chrome</a>, <a rel="tag" href="http://impl.emented.com/tag/vision/">vision</a></span></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://impl.emented.com/2008/09/10/chrome-pushes-for-a-standards-based-web-a-challenge-to-silverlight-and-flash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google in the Limelight with Chrome and Android [Best of August &#039;08 #3-4]</title>
		<link>http://impl.emented.com/2008/09/02/google-in-the-limelight-with-chrome-and-android/</link>
		<comments>http://impl.emented.com/2008/09/02/google-in-the-limelight-with-chrome-and-android/#comments</comments>
		<pubDate>Tue, 02 Sep 2008 19:30:53 +0000</pubDate>
		<dc:creator>Jonas Bolinder</dc:creator>
				<category><![CDATA[Highlights]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[feeds]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[IE8]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[PR]]></category>
		<category><![CDATA[RSS]]></category>
		<category><![CDATA[social networks]]></category>

		<guid isPermaLink="false">http://impl.emented.com/?p=49</guid>
		<description><![CDATA[Google's Chrome browser. Things are looking better for Android. Some feed services. A faster JavaScript in Firefox. IE8 beta 2. BackType comment aggregation. Neighbors and friends. Embargoes.]]></description>
			<content:encoded><![CDATA[<p>This week's compilation of interesting posts actually covers the past two weeks, due to lack of blogging time for me last week. Unfortunately, this might happen more times this fall, which seems to be busy for me, with near full-time of consulting. However, you may always check out my <a href="http://www.google.com/reader/shared/09538317620661410536">Google Reader Shared Items</a>, which contain a few more items not making it to my weekly list. The shared items also appear on my <a href="http://friendfeed.com/jobol">FriendFeed account</a>.</p>
<ul>
<li>The greatest news this week (and perhaps this year) is of course <a href="http://impl.emented.com/2008/09/02/chrome-googles-first-steps-towards-an-operating-system/">Google's launch of the browser Chrome</a>. The news broke while I was finishing the list below, and it puts some of the items in a different perspective, particularly the one about the launch of IE8 beta 2 below.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/chrome/">Chrome</a></span></li>
<li>Last month, I wrote about some <a href="http://impl.emented.com/2008/07/21/microsoft-plummets-on-search-android-in-trouble/">troubles for Google's Android mobile platform</a>. These <a href="http://ostatic.com/171128-blog/android-revs-sdk-promises-source-code">problems seem now to be history</a>, with the release of a new 0.9 version of the SDK, which is expected to be quite similar to the 1.0 version running on the first phones. Google is now also improving on the communication side, with the release of a <a href="http://code.google.com/android/roadmap.html">developer roadmap</a>, which promises a 1.0 SDK release and retail phones by Q4 this year. Actually, there are already rumors floating about an <a href="http://www.readwriteweb.com/archives/first_android_phone_just_approved.php">Android phone by HTC</a>, the "Dream", slated for November 10th.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/android/">Android</a></span></li>
<li>Marshall Kirkpatrick writes about <a href="http://feed.informer.com/">feed.informer</a>, formerly known as Feed Digest, a web service for <a href="http://www.readwriteweb.com/archives/feedinformer_relaunches_its_al.php">mashing, filtering and publishing RSS feeds</a>. As mentioned by Marshall, the site has some faults. For example, I found that the link to the Docs &amp; FAQs page is broken. Another provider of similar services is <a href="http://pipes.yahoo.com/">Yahoo Pipes</a>. For self hosting, the PHP RSS library <a href="http://simplepie.org/">SimplePie</a> provides detailed functionality for parsing feeds, though there seems to be no built-in functionality for keyword filtering. SimplePie on this page <a href="http://simplepie.org/wiki/faq/why_would_i_use_simplepie_over_something_else">compare themselves</a> to a few competing libraries.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/feeds/">feeds</a>, <a rel="tag" href="http://impl.emented.com/tag/rss/">RSS</a></span></li>
<li>From the JavaScript/Firefox department there were reports on progress in <a href="http://arstechnica.com/news.ars/post/20080822-firefox-to-get-massive-javascript-performance-boost.html">improving the JavaScript execution speed in Firefox</a>, leveraging a technique known as tracing optimization, hence the project code name Tracemonkey. Ars explains the basic idea behind tracing:<br />
<blockquote><p>The tracing mechanism records the path of execution at runtime and generates compiled code that can be used next time that a particular path is reached. This makes it possible to flatten out loops and nested method calls into a linear stream of instructions that is more conducive to conventional optimization techniques.</p></blockquote>
<p>The goal is to achieve execution speed comparable to native code, taking JavaScript performance into "the next tier", and "redefining the boundaries of client-side performance." Wonder how this improvement compares to <a href="http://impl.emented.com/2008/09/02/chrome-googles-first-steps-towards-an-operating-system/">Google Chrome's new V8 JavaScript Engine</a>?<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/firefox/">Firefox</a>, <a rel="tag" href="http://impl.emented.com/tag/javascript/">JavaScript</a></span></li>
<li><a href="http://blogs.zdnet.com/Bott/?p=518">Internet Explorer 8 is getting closer to official</a>, with a Beta 2 release just being announced. It's a massive makeover according to Ed Bott, with improvements in usability, privacy, standards compliance and new features like Accelerators, which are kind of smart shortcuts that perform a task, e.g. search, on selected text, and Web Slices, which provide a kind of subscription to a part of a web page that updates frequently. It's up to the developer to slice-enable particular web pages, by adding appropriate markup. The standards compliance is of course exciting, and it will eventually make the life easier for developers. Though it will take several years, with about <a href="http://www.w3counter.com/globalstats.php">one third of web surfers still using IE6</a>.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/ie8/">IE8</a></span></li>
<li><a href="http://www.backtype.com/">BackType</a> is a new comment aggregation service, <a href="http://www.techcrunch.com/2008/08/27/backtype-a-twitter-for-comments/">liked a lot</a> by Michael Arrington. Comments are automatically collected around the web, and can be searched for based on people or subject. You claim your comments by creating a profile and indicating which url you use when commenting. This is <a href="http://www.backtype.com/jobol">my profile</a>. I think it's a nice idea, with an open approach. Blogs can keep their comment system of choice, and still being included. No need for JavaScript solutions à la Disqus (<a href="http://www.disqus.com/people/jobol/">my profile</a>), for example.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/comments/">comments</a></span></li>
<li>Fred Wilson suggests that <a href="http://www.avc.com/a_vc/2008/08/friends-and-nei.html">social sites start using the concept of neighbors</a>, which are automatically discovered people with similar interests like you, instead of relying on so-called friends or followers and the habit of befriending or follow people. Seems like a practical idea to me, not having to manually look for friends, but have them automatically suggested.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/social-networks/">social networks</a></span></li>
<li>Marshall Kirkpatrick explains the <a href="http://www.readwriteweb.com/archives/why_and_how_embargoes_work_in.php">concept of embargoes in blogging</a> and why it generally is a better idea than exclusives. An embargo works as an agreement between bloggers and a company not to write about a new product or service until a specific time. This has several advantages, such as a broader and deeper coverage from multiple perspectives.<br />
<span class="tags">Tags: <a rel="tag" href="http://impl.emented.com/tag/blogging/">blogging</a>, <a rel="tag" href="http://impl.emented.com/tag/pr/">PR</a></span></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://impl.emented.com/2008/09/02/google-in-the-limelight-with-chrome-and-android/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
