At 1:34 AM -0500 5/3/2010, Stephen Conrad wrote:
G4 Quicksilver running OS X 10.4.11
Opera prompted me that an upgrade was available so I grabbed it.
Now Opera won't work
"won't work" -- in what way? Flat tire? Stuttering engine? or did
it burst into flame at the end of your driveway?
Did you try removing your InputManagers and Internet Plug-ins?
Did you try totally removing all the support and preference files
that Opera poops around?
Will this version work on this machine?
OS requirement notwithstanding.... I've been playing with Opera...
First, the archive (dmg) available from Opera's main web page [*]
contains version 10.53.8339, built on April 22, even tho the archive
is dated April 26. This version is NOT what they tested in the
final beta; it is several revs later - IOW *untested* and days old.
<http://www.opera.com/>
Next, the archive currently available on Opera's beta page contains
version 10.53.8343, built on April 28. The archive itself is dated
April 29th.
<http://www.opera.com/browser/next/>
On my Macs, version 10.52.8339 crashes and hangs often. When it does
work, it's noticeably slower than Safari.
Version 10.52.8343 seems better, but in an few hours testing has
already crashed multiple times.
I'm currently using Flash 10,1,53,21 (aka 10.1rc2), btw. No other
non-standard plug-ins and no inputmanagers.
[*] I feel it's necessary to take note of the name of Opera's
archives - a first warning bell, as it were. The use of underscores
and "Setup" is telling .... that's a windoze thing. And the rest of
Opera feels, to me, like a bad port. This is DEFINITELY *NOT* a Mac
OS X native application and its poor stability proves they didn't
even bother to put in the effort to do basic debugging!
Ok,,, my eratta from trying to use 10.52.8343 on my 300-MHz Smurf
running Tiger...
- First launch took 45 seconds to display the main window. Safari: 10 secs.
- Said main widow is sized improperly, stuck half-way under the dock.
Safari: sized properly.
- It required another 30 seconds to populate the main window.
- Each time I try to select, copy, or edit the url field in the
address bar, I get a SPOD for a few seconds, then the edit operation
fails. No matter how many times I tried to select the whole URL, I
only got portions. After letting the browser sit idle for half a
minute, with the cursor at the end of the URL, I was finally able to
type into the field and copy newly typed text (but not the text
already there!). These problems tell me that they're not using the
OS' normal text handling services - yet another sign of a bad port.
- When I hit tab, to move from the address to the search field, there
is a delay of about 4 seconds before the cursor moves. Safari and
Firefox don't have this lag at all.
- Import bookmarks from Safari. Even tho I specifically selected the
correct import item, it presented a dialog pointing to Documents, not
to the proper place in ~/Library. Yet another sign of a bad port.
Upon selecting my Bookmarks.plist, Opera gave me a SPOD. It took
five minutes for the SPOD to clear. 2723 bookmarks imported.
(Firefox does the import in under a minute). Looks like Opera got my
whole folder structure, but what's there is now sorted alphabetically
- totally destroying the logical order I'd created in Safari.
- Almost two minute of SPOD when I closed the Bookmarks tab.
- heh. Every tab I close results in a SPOD for about a minute or two.
- oops. It crashed when I closed the last tab.
- oops. It crashed when I went to view APOD. That's just pitiful.
Pages don't get much simpler than APOD.
<http://antwrp.gsfc.nasa.gov/apod/astropix.html>
- oops. It crashed when I went to view the Acid3 test.
- oops. It hung at 8/100 on Acid3 when I retried.
- Ok. It finished Acid3, 100/100. However, the results are not pixel
perfect. Safari also gets 100/100, is pixel perfect, and completes
the test about 15 seconds faster.
- Timing has been subjective. Let's get some real objective numbers,
by running Sunspider.
<http://www2.webkit.org/perf/sunspider-0.9/sunspider.html>
Opera 10.52.8343: 75753.4 ms
Firefox 3.6.4: 35172.0 ms (a recent nightly build)
Safari 4.0.5: 33301.6 ms
WebKit Nightly: 28363.6 ms (nightly build of 2 May).
My conclusion: This is a pig browser backed by a company with a
great PR machine (oh! it's so fast!). I wouldn't recommend this pile
of padadodo to anyone. In short - don't waste your time. Use real
browsers instead, like Safari and Firefox and iCab and ...
YMMV.
- Dan.
--
- Psychoceramic Emeritus; South Jersey, USA, Earth.
--
You received this message because you are a member of G-Group, a group for
those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs.
The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette
guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/g3-5-list
