Commentary

Serdar Yegulalp
 

Google Chrome: A Point of Departure

Google Chrome officially got ratcheted up to a 1.0 release earlier today. The feature set may be meager compared with Firefox (e.g.: no plug-ins, yet), but it's only a starting point. And not just for something to be decked out with plug-ins, either.

Google Chrome officially got ratcheted up to a 1.0 release earlier today. The feature set may be meager compared with Firefox (e.g.: no plug-ins, yet), but it's only a starting point. And not just for something to be decked out with plug-ins, either.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This all started with some thought about the whole concept of "small is beautiful" or "less is more" -- however you want to put it -- in programming. It's a good place to start, but you can't always stay there. Users badger the programmers for this or that pet feature, and before long what started as a lean-and-mean piece of work has become top-heavy and potentially unstable. And soon a competitor comes along, someone who's stuck with the original plan of Keep It Simple, Silly, and you're back to where you started.

Here's where I think open source can be a big help, and I'll start with an open source project that's been constantly accused of succumbing to unneeded bloat: Firefox. It's not hard to expand on the core functionality of Firefox by writing extensions, but throw in too many and problems can arise. The folks at Flock took the Firefox source code and added a whole slew of social-networking extensions that would nominally be accomplished through plug-ins, but integrated them into the core as cleanly and efficiently as possible. If you want all that stuff, pick Flock; if you want to go with the original, go with Firefox. And any fixes that benefit one can in theory (and, typically, in practice) benefit both.

I'm seeing a similar future for Chrome, too. Rather than have a one-size-fits-all version, the Chrome we're getting now is going to be a point of departure for other projects that see the browser as a malleable vehicle, not a fixed destination. The same could be said of any number of other programs that serve as a major focal point for open source activity: OpenOffice, for instance, already has some of this going on with Symphony.

So while I welcome Chrome 1.0 and give it a place of honor on my desktop -- right alongside Firefox and Flock themselves -- I'm really looking forward to what happens when the legions of open source creators sink their fingers into it.


Follow me on Twitter: http://twitter.com/syegulalp


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links