Firefox vs Chrome

Chrome Needs Color Management
Image by wabisabi2015 via Flickr

We’ve just recently returned to Firefox after some time with Chromium, Chrome’s open-source brother.

In the time since we’ve left, Firefox has iterated so fast. In the last calendar year, it has gone from Version 4 to Version 9. It did so mostly by eliminating minor version numbers. Every version is now a major version.

Over the last year, there have been a lot of changes. Firefox 4 was the first to bundle Firefox Sync, which syncs browser settings. The speed of Firefox has increased sevenfold, and the memory usage, a common complaint about Firefox, is down 50%.

The Browser Wars are an arms race to see who can make their browser faster. Recently, Chrome overtook Firefox for the first time. But it has issues, despite its features.

Chrome creates a separate process for each tab, which protects against any single failure bringing down the whole browser. However, this can have pros and cons. Both Firefox and Chrome have reputations for memory issues, although Firefox is more famous for this, the two browsers use more or less memory at different times, because of this design. Firefox has made a good push to reduce its memory usage.

While our situation might not be typical, the new Firefox is definitely seeming more snappy than it once was. There are things in Chrome that are not currently available in Firefox. One of the nicer ones, although Chrome unfairly calls it an App, are the large bookmarks of commonly used programs on the Blank New Tab menu. We’ve been able to reproduce this in Firefox, however, using a plugin called Fast Dial, which creates the same sort of visual bookmarks.

We aren’t the only ones who enjoy Firefox, while looking for some, but not all, of the features of Chrome. We located a Firefox extension to enable the HTML5 desktop notifications according to the API Chrome implements. This allows an open Gmail window, for example, to pop up a notification.

So, in the end, Chrome and Firefox both offer compelling features, and we’ll keep them both installed, but we keep running back to Firefox. It just suits us. And it suits many others.

What do you use and why?

Moving Back to RSS from Twitter

This icon, known as the "feed icon" ...
Image via Wikipedia

It is amazing that we would come full circle from where we were when we started with Twitter in January of 2009. When we began using Twitter, part of the appeal was as a real-time replacement for RSS reading. But, recently, we’ve returned to RSS feed reading as a much more reliable manner of ensuring we get our news.

That does not mean Twitter is not still a big part of our news delivery, but it has become overwhelming. But if your feed consists of nothing but your news feed piped into Twitter, then we will now go back to following you in Google Reader. We will now take advantage of the greatest benefit of Twitter to someone looking to get news and information…curation. The most valuable stories will float to the top as people tweet them.This will make Twitter much more social for us.

In January, an article made the rounds, maintaining that RSS was being ignored, and we should be worried. Google Chrome has no native RSS support built in, Mozilla is killing off the RSS icon in Firefox 4.0. How RSS integrated into systems may need to be rethought. Google Reader is all well and good, but that is a website, not a browser. That same article has some good suggestions.

  • Why can’t, when you visit a blog article, the browser reads the comments RSS, and when you next come back to that article, it can tell you that there have been new comments since, and highlight them on the page?
  • Why do we go through the same daily routine of checking certain sites over and over again? Can’t our computers be more intelligent here? Isn’t the purpose of the computer / browser to save us time!? Why doesn’t the browser, when you open it, tell you how many new items there are, on what sites you commonly visit, without you having ever configured this?

Dan Frommer, on Business Insider, countered that RSS is not dying, normal people never used it. In his opinion, RSS is a fine backend technology. In fact, many who moved to Twitter are reading feeds pumped to Twitter from RSS. That using RSS in an RSS reader has never been mainstream, which is valid. O’Reilly points out, as a backend technology, RSS never blocks you or goes down.

We wanted there to be a Twitter alternative, and there very well might be. Twitter is a stream. Twitter Lists would allow everything to be neatly organized in an intuitive way,  but the issue is that there is no adequate solution to reading longer and in-depth on your desired sources for Twitter. There is paper.li and the Twitter Times. There are social feed readers. We will be exploring these at some future point for discussion. But magazine/newspaper like feed readers seem to be the rage right now.

What do you think?