Dan Kantor

Tue, Mar 9th

Love the Biggie flowing through my music stream today

Firefox Is Losing The Race To Chrome

Many people have asked me why I started developing ExtensionFM on Chrome before Firefox. Firefox has about 25% market share while Chrome has only 5%. Below are ten reasons why I believe Chrome is the better browser right now and easier to develop applications for.

Let me first say that I have had a love affair with Firefox for the past five years. I started using it in the summer of 2005 when I was, ironically enough, an intern at Microsoft. I want Mozilla to succeed. It is important to have a ‘non-biased’ company in the browser space. But right now, they are getting their butts kicked by Chrome (and its Webkit cousins).

Here are 10 reasons (with 1 bonus) why Chrome has surpassed Firefox.

Speed: Chrome renders pages faster than Firefox. On Mac it is even more noticeable.
Weight: Chrome uses a lot less memory and system resources than Firefox.
HTML5: Both Chrome and Firefox have implemented a bunch of HTML5 features. There are still many more to come. To this point however, each has implemented a different set of features. The set of features that Webkit has implemented are more important at this point - WebDatabase, WebSockets, etc.
CSS3: Related and equally important to HTML5 is CSS3. At this point Webkit has implemented a lot more of the spec, including multiple backgrounds and background gradients.
Extensions: Chrome extensions do not require a restart on install or when they update. Firefox’s do. Right now Firefox has more extensions. But all the good ones will come to Chrome. Chrome also makes it really easy for developers to package extensions for delivery in the gallery or on a third party site.
Video Support: As part of the HTML5 video element, browsers can now create a native video player that is controlled by Javascript (thus bypassing Flash). But this means very little if the video player does not support the leading codec - H.264. Chrome supports this, Firefox does not (b/c of licensing reasons).
Audio Support: Equal to the video element above, HTML5 introduced an audio element that is a native player controlled by Javascript. But as with video support, audio support is only as good as the codecs it ships to play back different formats of music. Unbelievably, Firefox does not ship a codec that supports MP3. Let me repeat that. Firefox does not support MP3. They only support the open source and far less used OGG format. Chrome of course supports MP3 (as well as OGG).
Startup: On both Mac and PC, Chrome starts up a lot faster than Firefox.
UI: Chrome has a very minimal look with only the basic “chrome” surrounding the web window. Firefox looks more bloated. Even Mozilla recognizes this. The next version looks a lot more like Chrome.
Threaded Tabs: When a tab in Chrome crashes, it does not freeze or crash the entire browser. This is because each tab runs in its own process. All Firefox tabs run in the same process. If one tab crashes, it brings down the entire browser.
Mobile (Bonus): Here is a list of companies that ship mobile devices with a Webkit browser: Apple, Google, Palm, RIM (coming), Nokia. Here is a list of companies that ship a mobile device with a Firefox browser: None.

Like I said in the beginning, I love Firefox and want them to succeed. But you can not ignore the 11 important facts I have listed above. Firefox is losing to Chrome (and its Webkit cousins). Mozilla knows this. I want Firefox to succeed and I believe that it can. The best part about Google (and Apple via Webkit) entering the browser market is that they have pushed the rate of innovation to never before seen heights. Let’s hope this continues for many years to come. Right now, however, I am choosing Chrome as the browser to develop for.

Comments (View)

7 notes

RT @cashmusic: The new @familyoftheyear EP, Through The Trees is out now, available directly from the band at http://familyoftheyear.net/

Comments (View)

Mon, Mar 8th

RT @extensionfm: New Release: Auto-updating sites and the music activity stream - http://bit.ly/9nNu6R

Comments (View)

ExtensionFM New Release: Auto-Updating Sites and the Music Activity Stream

extensionfm:

The latest release (3.2) introduces auto-updating sites. This means that songs will automatically be added to your library, from the sites you have already visited, as those sites post them. You do not have to re-visit sites to get new songs. This all happens in the background.

The All Songs List view has been tweaked a little with timestamps to better reflect this new ‘Music Activity Stream’:

All sites have auto-updating turned on by default. You can turn this off on a site-by-site basis by right-clicking on a site in the All Songs Pane View:

You can now also remove an entire site and all of its songs by right-clicking and choosing delete:

If you would like to remove individual songs, you can still right-click on any song in All Songs Pane view and choose delete. If you remove all the songs from a site, the site will still remain and continue to auto-update if you have not chosen to turn that off

Comments (View)

22 notes

RT @tnw_apps: Extension.fm, the must have music add-on for Chrome http://tnw.to/15miY by @thomcummings

Comments (View)

Sat, Mar 6th

RT @albertwenger: Doing some reading online and discovering new music courtesy of http://extension.fm and http://hypem.tumblr.com

Comments (View)

1 note

Fri, Mar 5th

ps - just bought it on Amazon

Comments (View)

Portugal. the Man came out with a new album this week! There needs to be a better way to learn about these things. Its not on Spotify yet :(

Comments (View)

1 note

RT @rstaicut: It’s a great day for BeeMe! Testing today and getting ready to launch at our first coffee shop on Monday.

Comments (View)