Commentary
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
- How To Regain IT Control In An Increasingly Mobile World - by BlackBerry
- The BlackBerry PlayBook tablet's Good Bones - by BlackBerry
Reports
More >>Webcasts
- Maximize ROI with Database Consolidation onto Private Clouds
- The ABC's of Cloud Computing in the Midmarket
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
| 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: 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 RSSResource Links
This Week's Issue
Technology Whitepapers
- Mobile BI: Actionable Intelligence for the Agile Enterprise
- Creating the Enterprise-Class Tablet Environment - by Yankee Group
- The BlackBerry PlayBook tablet's Good Bones - by BlackBerry
- Red Alert: Why Tablet Security Matters - by BlackBerry
- New Visual and Wizard-Driven Paradigms for Exploring Data and Developing Analytic Workflows
Featured Broadcast
This white paper explains how to create a manageable, scalable environment suited to answer real-time business needs by building out a data center on a standards-based, virtualization-aware, energy-efficient and affordable platform. Plus, learn how virtualization is making the jump from the server realm into the application, mobile and database worlds in the additional resources section.
Learn More












