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.
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.
Google should not be making Mac and Linux users wait for Chrome.
There’s a significant guerrilla-marketing campaign in action – the officially unstated competition with Microsoft for ‘world domination’. First Apple (with Safari), and now Google (with Chrome), is besting Microsoft Internet Explorer on Windows platforms. In revisiting the browser wars of the late nineties, it’s crucial for Google Chrome to go toe-to-toe with the competition. And whether we like to admit it or not, that competition is Microsoft Internet Explorer on the Microsoft Windows platform.
The Mac and Linux ports will come from the Open Source’ing of Chrome … and we need to wait for this … Optimistically, that’s short-term pain, long-term gain.
It’s 2008, not 1998. In the past, as an acknowledged fringe community, Mac users were accustomed to the 6-18 month lag in software availability. Linux users, on the other hand, were often satiated by me-too feature/functionality made available by the Open Source community. In 2008, however, we have come to expect support to appear simultaneously on Mac, Linux and Windows platforms. For example, Open Source Mozilla releases their flagship Firefox browser (as well as their Thunderbird email application) simultaneously on Mac and Linux as well as Windows platforms. Why not Chrome?
So, what should Google do in the interim:
Provide progress updates on a regular basis. Google requested email addresses from those Mac and Linux users interested in Chrome … Now they need to use them!
Commence work on ‘Browser War’ commercials. Apple’s purposefully understated commercials exploit weaknesses inherent in Microsoft-based PCs to promote their Macs. Microsoft’s fired back with (The Real) Bill Gates and comedian Jerry Seinfeld to … well … confuse us??? Shift to browsers. Enter Google. Enter Mozilla. Just think how much fun we’d all have! Surely Google can afford a few million to air an ad during Super Bowl XLII! Excessive? Fine. I’ll take the YouTube viral version at a fraction of the cost then … Just do it!
For now, the Pareto (80-20) principle remains in play. And although this drives a laser-sharp focus on Microsoft Internet Explorer on the Microsoft Windows platform at the outset, Google has to shift swiftly to Mac and Linux to really close on the disruptiveness of Chrome’s competitive volley.
Our manuscript on annotation modeling is one step closer to publication now, as late last night my co-authors and I received sign-off on the copy-editing phase. The journal, Computers and Geosciences, is now preparing proofs.
For the most part then, as authors, we’re essentially done.
However, we may not be able to resist the urge to include a “Note Added in Proof”. At the very least, this note will allude to:
The work being done to refactor Annozilla for use in a Firefox 3 context; and
How annotation is figuring in OWL2 (Google “W3C OWL2” for more).
What a difference a day makes!
Yesterday I learned that my paper on semantic platforms was rejected.
Today, however, the news was better as a manuscript on annotation modeling was
accepted for publication.
It’s been a long road for this paper:
The initial reviews called for major revisions. With tremendous support from my co-authors, the paper was significantly revised, and re-submitted.
After some additional interactions, I just learned that the paper was finally accepted for publication.
The abstract of the paper is as follows:
Annotation Modeling with Formal Ontologies:
Implications for Informal Ontologies
L. I. Lumb, J. R. Freemantle, J. I. Lederman & K. D.
 Computing and Network Services, York University, 4700 Keele Street,
Toronto, Ontario, M3J 1P3, Canada
 Earth & Space Science and Engineering, York University, 4700 Keele
Street, Toronto, Ontario, M3J 1P3, Canada
Knowledge representation is increasingly recognized as an important component of any cyberinfrastructure (CI). In order to expediently address scientiﬁc needs, geoscientists continue to leverage the standards and implementations emerging from the World Wide Web Consortium’s (W3C) Semantic Web effort. In an ongoing investigation, previous efforts have been aimed towards the development of a semantic framework for the Global Geodynamics Project (GGP). In contrast to other efforts, the approach taken has emphasized the development of informal ontologies, i.e., ontologies that are derived from the successive extraction of Resource Description Format (RDF) representations from eXtensible Markup Language (XML), and then Web Ontology Language (OWL) from RDF. To better understand the challenges and opportunities for incorporating annotations into the emerging semantic framework, the present effort focuses on knowledge-representation modeling involving formal ontologies. Although OWL’s internal mechanism for annotation is constrained to ensure computational completeness and decidability, externally originating annotations based on the XML Pointer Language (XPointer) can easily violate these constraints. Thus the effort of modeling with formal ontologies allows for recommendations applicable to the case of incorporating annotations into informal ontologies.
I expect the whole paper will be made available in the not-too-distant future …
The UI – Of course. However, this is another area where Firefox 3 has made significant headway. Even on a Mac, Firefox 3’s UI is also elegant and clean. (For an amusing take on the Apple UI paradigm, have a look at this Eric Burke cartoon. I’m not sure how Burke would represent the Mozilla UI … However, one thing’s for sure, it’s become a lot more elegant and cleaner over the years.)
Find – The Firefox 3 implementation looks remarkably like Safari’s.
Resizable text areas – Excellent. Not sure if Firefox 3 has this.
Safari 3.1 also presents a twofold irony with respect to Web standards:
You need to do a little digging (page 8 of the Safari Product Overview) to determine what is meant by Web standards support. And once you do, you’ll learn that it relates to CSS, HTML 5 and SVG. Of these, “HTML 5 offline storage support” has the potential to be most interesting, as Google is analogously demonstrating with Google Gears. So, it’s ironic you need to dig for something that has such value.
In it’s support of HTML 5, we have a commercial entity (Apple) leading the way in terms of implementing standards. This is refreshing in general, and in particular in Apple’s case, as traditional expectations would have the Open Source implementations (e.g., Firefox) ahead in this regard. To quote Alanis Morissette: “Isn’t it ironic… don’t you think?”
When you factor in support for Windows, and apparently frequent releases, it’s no wonder that Safari is gaining momentum at the expense of Microsoft Internet Explorer (IE) and Firefox.
And not that I’ve been following developments with IE, but one has to wonder, if we are to re-visit the IE vs. Netscape browser wars of yesteryear, might the combatants this time be Apple Safari 3.x and Mozilla Firefox 3.x?
One can only hope!
I’ve just upgraded to Firefox 3 Beta 4.
The spreadsheets component of Google Docs appears to work now. And although this suggests improvements in AJAX support, a known issue with GMail contacts remains:
GMail (new version) conversation labels appear on their own row in the message list, and names don’t show in the contacts manager (bug 415252)
This GMail bug remains a showstopper for me.
Of course, it’s important to remember that
Firefox 3 Beta 4 is a developer preview release of Mozilla’s next generation Firefox browser and is being made available for testing purposes only.
I just downloaded Firefox 3 Beta 3 for Mac OS X Leopard.
My initial impressions are as follows:
It looks great!
It’s fast! In some cases, blazingly fast! Page renderings, downloads, etc.
Its AJAX support is very weak! This is a showstopper for me, as I use a number of AJAX-based applications. Although the word processing aspect of Google Docs appears to work, the spreadsheet capability isn’t quite there yet. And surprisingly, when I opened my GMail contacts, none of them appeared!
Its add-on support is weak. This isn’t too surprising, I suppose, and is perhaps somewhat unfair to mention at this point. However, none of my add-ons work with this release, so I thought it was worth noting.
Looks highly promising, but don’t uninstall Firefox 2 (or your current production browser) just yet.