Google Chrome for Linux on Bright Hub: Series Expanded

I recently posted on a new article series on Google Chrome for Linux that I’ve been developing over on Bright Hub. My exploration has turned out to be more engaging than I anticipated! At the moment, there are six articles in the series:

I anticipate a few more …

It’s also important to share that Google Chrome for Linux does not yet exist as an end-user application. Under the auspices of the Chromium Project, however, there is a significant amount of work underway. And because this work is taking place out in the open (Chromiun is an Open Source Project), now is an excellent time to engage – especially for serious enthusiasts.

Stainless Improving By Leaps and Bounds!

When I first wrote about Stainless, I indicated that it provided impressive features/functionalities for a version 0.1 release. In a subsequent post, I elaborated on Stainless’ strengths and weaknesses. 

Stainless is now at version 0.2.5. And in the space of a few weeks, Mesa Dynamics has addressed a number of the weaknesses I previously noted. Specifically:

  • Download capability – It just works now! Thanks!
  • Offline mode – Via Google Gears. Interestingly, I predicted this might take some time. I am so happy to be wrong!!
The release notes for Stainless provide the details on these and numerous other improvements.
So, what’s left? In order for me to shift to Stainless as my ‘production browser’, I really need:
  • Interaction with Google Notebook – Even via the bookmarklet is fine! 
  • URL Caching/Auto-Completion – As noted previously … 
Even with these production must-haves, Stainless is well worth a look today.

What You Will/Won’t Get with Stainless

Earlier today, I started to evaluate Stainless. In this post, it’s my intention to dig a little deeper by sharing more of what you will and won’t get with Stainless.

What you will get:
  • Private Browsing – On selecting “File \ New Private Browsing Window”, the Stainless browser that appears makes use of WebKit‘s private browsing mode. In this mode, global history, page caching and storing of AutoFill information are disabled. Spawned tabs and windows inherit the private-browsing mode.
  • Single-Point-of-Entry – Obviously you can type in a URL. However, you can also type in a text string (e.g., “Google Chrome”) to initiate a search via Google. In fact, via Stainless’ “Preferences”, you can choose to make use of Google, Yahoo!, Live Search, AOL or Ask.
  • Process Management – I alluded to the multiprocess capability of Stainless in the previous post. I’ve just realized that by selecting “Window \ Process Manager” you can monitor and even terminate processes via a simple GUI. Very nice!
What you (likely) won’t get:
  • Downloading Capability – I tried to download from a few sites … and all attempts FAILED!! I am shocked and amazed. I saw a Page loading error: Frame load interrupted message appear in the status bar each time … This is disappointing and will hopefully be fixed in version 0.2.
  • History – Via Stainless’ “Back” button, there is some notion of history, but that’s it.
  • URL Caching/Auto-Completion – URL caching and auto-completion are unavailable.
  • An Open Source Version – There’s a significant Open Source aspect to Chrome. Based on proprietary technology developed by Mesa Dynamics for their Hypercube personal-widgetsphere offering, Stainless and Open Source seem unlikely to resonate.
  • Cross-Platform Support – Stainless is available for Mac OS X Leopard. Will this offering will be broadened? Unknown.
  • Extensibility – This killer functionality is a core competence of Mozilla Firefox. It appears that Chrome will sport something analogous. Stainless? Unknown?
  • Offline Mode – I’m thinking of something along the lines of Google Gears … but I don’t see it arriving soon … I installed Gears for Safari. Unfortunately, Stainless gives me the impression that I have Gears support, but in reality (during an offline situation) it’s clear that I don’t. Misleading.

Despite the negatives, I expect to continue to make use of Stainless, and encourage you to do the same.

Feel free to chime in with your impressions.

Chrome Today the Stainless Way

Even though I recently whined about the wait for Google Chrome on Mac and Linux platforms, I haven’t spent any effort empowering some other browser with Chrome-like features/functionalities – even though this is possible. And although CrossOver Chromium caught my attention, I wasn’t sufficiently motivated to evaluate it either.

Somewhat surprising then is the fact that I have gravitated rapidly towards a quick-and-dirty evaluation of “Stainless – a multiprocess browser for OS X inspired by Google Chrome.” Inspired is definitely the operative word here as:

… the Mac version of Chrome will use a WebCore-rendered bitmap to pass between the browser and rendering processes. The strategy we use in Hypercube (and now Stainless) is far less ambitious, but a whole lot easier to do and, thus, available today for your downloading pleasure (for Leopard only, sorry).

And what a pleasure it is!
Honestly, based on the recent LifeHacker post, I expected a whole lot less than what Stainless actually delivers today – in version 0.1!

Based on about 30-minutes experience, Stainless:
  • Performs well – It loads Web pages quickly. And as “ps -alx | grep -i stainless” indicates, Stainless really is a multiprocess browser for OS X. For me, this alone makes Stainless worth the effort.
  • Supports AJAX – I’m writing this blog post using Google Docs via Stainless. Stainless worked fine on my initial tests with other Google productivity apps – I tested Google Spreadsheets and GMail. I therefore have some level of comfort in proclaiming it as supporting AJAX. Nice!
I’m sure I’ll have more to say soon … In the meantime, though, even at this early stage Stainless is definitely worth a serious look.