Webstractions - Web Development & Design News

Firefox is experiencing growing pains in more ways than one and two of the bloating problems they have encountered appear to be intertwined -- browser code and Google money. The browser war may be pushing the Firefox project too fast and down the wrong path.



Recent estimates place Firefox with a little over 15 percent of the market and Internet Explorer around 78 percent. Most of the market share that Firefox has gained on Internet Explorer came with the royalty deal that Google struck with the now for-profit Mozilla Foundation, who has 90 employees and revenue of more than $100 million in the last couple of years.

Mozilla plans to make enough money to keep growing ... Google, which, like the other search companies, is always competing for better placement on browsers. Under the agreement, the Google search page is the default home page when a user first installs Firefox, and is the default in the search bar. (Google has a similar placement with Apple’s Safari.)

The transparency of Mozilla is coming into question by many critics, mostly because of the level of secrecy that has to be maintained in its arrangements with Google. That issue caused tension around getting the deal done and disclosure.



Other critics claim that Mozilla is percieved as an extension of Google:

... they note that one of Google’s growth areas, Web-based software applications, would have a better chance of success with a browser not controlled by its biggest rival, Microsoft.

With money comes change. Firefox is evolving in directions that nobody would have imagined a couple of years ago.



The surge in popularity of Firefox has caused a backlash effect from Microsoft who is shelling more money into the advancement of Internet Explorer. The release of IE 7 shown remarkable improvements over previous versions and demonstrated to the Google/Mozilla camp exactly what they are capable of accomplishing.



When Firefox launched over five years ago, "it burst on the open-source browser scene like a young Elvis Presley -- slim, sexy and dangerous.", says Scot Gilbertson of Wired. But now he fears that with the "IE killing" release of Firefox 3.0 later this year will be in danger of becoming

the later version of Elvis -- fat.

Anecdotal reports of problems, from sluggishness to slow page loads and frequent crashes, have begun circulating in web forums, along with increasingly loud calls for Firefox to return to its roots. The alleged culprit: bloat, the same problem that once plagued Mozilla, the slow, overstuffed open-source browser spawned by Netscape that Firefox was originally meant to replace.

The "roots" was Firefox's small memory footprint, fast load time and extensibility thru plugins. It was a roll-your-own bare bones browser. It was this root that became one of Firefox's major selling points to non-geeky computer users. But now that is coming under more scrutiny as reports from reader polls cite that Firefox's mysterious habit of gobbling up huge chunks of memory as their number one complaint.

Actual data is hard to come by, but Mike Schroepfer (Mozilla's vice president of engineering) opines that memory problems can be blamed on the users environment which is influenced by other software, add-ons, and extensions. To keep the bulk down, Schroepfer's team sets a high threshold for the addition of features. New features aren't built in unless they are useful to at least 90 percent of Firefox's users.

Despite those safeguards, some now-standard features could be adversely affecting performance.

Firefox's page-cache mechanism, for example, introduced in version 1.5, stores the last eight visited pages in the computer's memory. Caching pages in memory allows faster back browsing, but it can also leave a lot less memory for other applications to use. Less available RAM equals a less-responsive computer.

It is a fine line that Firefox has to walk when trying to find a balance between what is perceived to be a "needed" feature and one that is not. What is too much? And does Firefox have a choice in that matter?

Slowly but surely, Internet Explorer is catching up to Firefox. In IE7, Microsoft added tabbed browsing and integrated RSS support to its browser. If Firefox is going to continue to compete, it will need to up the ante, but it must do so without making users add extensions .. and possibly introduce compatibility problems.

With the emerging technologies appearing on the web today, it will certainly push the limits of the new breed of browsers, Firefox and Internet Explorer. The change is inevitable and I do believe that neither will be going back to their roots and will continue to grow with the web.



Technorati Tags: firefox, internet, explorer, google, bloat, money, code, extensions

Labels: bloat, code, explorer, extensions, Firefox, google, internet, money

After seeing Carsten Cumbrowski's search goodies for BUMPzee and they only supported Internet Explorer, I took it upon myself to write a search plugin for Firefox.

Go to my BUMPzee search plugin page which has a one-click installation regardless of what version of Firefox you are using.

Firefox 2.0 and beyond supports the new OpenSearch format, while previous versions used Sherlock. The script will detect which version you are using and install the corresponding plugin for you.

Labels: bumpzee, extensions, Firefox, opensearch, plugin, search

If you do a lot of forum posting or blog commenting, most of it is done online with a provided textarea box from within a form. The textarea boxes are usually very tiny to post any extended length of commentary and causes you to continually scroll up, down, and even sideways just to review what you had just typed. Of course there is the "preview" option, but if there is a correction to make -- you still have to locate it inside of that miniscule box.

Enter Two Extensions to the Rescue

First there is the quick and dirty Resizeable Textarea extension which lets you resize virtually most textarea form boxes. The other, more bells, is a Resizable Form Field extension for textareas, as well as select boxes, text fields, and even iframes.

I use the Textarea only extension, and it works quite well. A little buggish at times, seems it will not work if open the form up in a new window. Another user reported the same thing, citing Gmail as an example, works well when composing in the main window, but doesn't work for the text area if you click the "open in new window" icon.

Have not tried the other flavor yet, and as of this post, there are no reviews. Asa Dotzler likes it though, even though there appears to be some abnormal behaviour with it -- such as form fields getting resized in other tabs.

Labels: blogging, extensions, Firefox

Yeppers. This is the Official Webware Top 10 List of lists. It was posted quite some time back by Rafe Needleman, but worth mentioning again.

The lists for About.com and Mozilla seemed to have vanished, but a pretty decent compilation of Top 10 Extension lists from Download.com, Irfan Habib, CyberNet, Simple Dollar and Moleskin . Depending on each list's slant, there should be one in there that will fit you just right.

Read/Write Web is Web 2.0 addons for Firefox, and probably the most impressive of the lot. They take a closer look at what web apps are using the browser as a platform.

The Lifehacker list was for top 10 tweaks.

And after you install all of those extensions, made all your tweaks, then you will need the Quick Online Tips list of extensions for managing ...ahem... extensions. I know I will.

Labels: extensions, Firefox, tweaks