Google Chrome: Is Opera in trouble?
Tuesday, 2. September 2008, 08:38:46
firefox, chrome, ie, opera
By now, most techies have heard about the impending launch of
Chrome, Google's open-source browser, sometime tomorrow (9/2/2009). A number of
tech bloggers have already explored how Chrome will affect Mozilla Firefox and Microsoft Internet Explorer. Predictably, there's a general consensus in opinion as to what Chrome means - namely, it is Google's way of eroding Microsoft's dominance in the browser market. However, as an Opera user, the more interesting question is how Chrome will affect Opera? Even prior to this announcement, Opera's growth on the desktop is limited. It's potential really lies in the mobile and embedded device markets. The folks who choose Opera over Firefox and Internet Explorer are looking for a different kind of experience. I believe Google's Chrome will become one of the dominant browsers in the coming years, and will establish a new equilibrium in the browser market, with the dominant players (Google, Microsoft and Mozilla) owning 90% of it. The 10% that is left over will be carved up by Opera, Safari, etc. Opera was never a serious competitor to Firefox or Internet Explorer. It is simply an alternative. The impact of Chrome on Opera will be minimal on the desktop, but Opera will face much greater challenges in the mobile space when Android or a mobile version of Chrome is released. The mobile space will be where the future of Opera is determined.
Alvin Tiamzon # 3. September 2008, 15:12
nacholibre # 4. September 2008, 01:40
So far, the reviews have been quite positive on Chrome, considering that it's still a 0.20 beta product.
Danny Boy, FCD # 4. September 2008, 05:00
Alvin Tiamzon # 4. September 2008, 13:56
Opera deserves a market share equal to that of Firefox. And with Chrome's release, I don't think it will be possible.
nacholibre # 4. September 2008, 14:42
Pier23 # 6. September 2008, 22:26
Once Google Gears is on the desktop, CTOs, CIOs can make the now easy-made leap to FREE Google "Office" while dumping paid Microsoft Office.
Opera does not grow because of serious design flaws.
Opera is not a platform.
Opera technologists see Opera as a "browser" and not as a way to display structured data based on return/reply protocols.
Opera should have a Proxy Engine or better a Messaging Engine, like the REBOL VM.
With such a foundation, rendering HTML pages in a "web browser" or emails in an "email client" or RSS feeds in a "feed reader" becomes a cinch.
Opera should make it easy to tap Web 2.0 APIs. Simply, programmers should need only learn the "Opera API" and let the folks at Opera make the glue code to tie into the APIs of Flickr, Delicious, Google Maps, Yahoo Upcoming, more.
Witness the explosion of streaming livefeed video. Combined with Youtube recorded video and you're seeing the future of the Internet.
Opera should ditch trying to compete by providing 1970s through 1990s era technology -- text emails, rendered HTML as a UI with the DOM and Javascript updating DOM objects, RSS text feeds.
Rather Opera ought to become the Video Browser -- video email, video calling, video livefeeds, recorded video.
If not, someone might get smart, take VLC and wrap it into something that folks shall call the Video Browser.
The future winner shall be the VIDEO GOOGLE search engine database provider with its Video Browser and brokering of LiveFeed Video.
kailapis # 7. September 2008, 04:31
nacholibre # 7. September 2008, 05:16
In addition, Opera faces a whole army of new competition from "derivative" browsers as well. People using derivative browsers are usually looking for something alternative, but remain compatible with the "main" browser in terms of rendering and layout. For example, in the case of Mozilla's Gecko, it is used in Firefox, Flock, Camino, etc. Or take Microsoft's Trident, it is used in IE, Maxthon, AvantBrowser, etc. The last major layout engine, WebKit, it is used by Safari, Chrome, Konqueror, etc. Opera's layout engine, Presto, is the only one that does not have any "derivative" browsers using it. That, I believe, will hinder the progress of Presto in terms of development and in usage.
Pier23 # 7. September 2008, 20:58
Here are some:
[1] autohotkey-like component
control keyboard shortcuts
[2] gmote-like component
control mouse gestures
[3] webkit
why waste resources on Presto? replace presto with webkit, which Google shall bankroll
[4] V8
why waste resources on other javascript vm's?
[5] rebol v3.0
rebol is so far ahead of web 2.0 javascript products
nacholibre # 9. September 2008, 14:52