glimmer
Plugins have always been a pain.
Use glimmerblocker, which is a kind of local proxy (but light and very efficient), and has been working flawlessly for me in between updates...
Apple's Safari 5 has been out for just one day, but — as is usual with integer-level upgrades — users are already reporting niggles, nuisances, and no-goes. Over on Macintouch, for example, we first learned of Safari 5's annoyance with third-party plug-ins, specifically SafariStand. Mike Solomon, the creator of the SIMBL ( …
Safari Stand uses a bunch of hacks and undocumented APIs to work. Why on earth should anyone expect it to work with Safari 5?
I've tried Safari 5 on my ThinkPad and am impressed with the extra speed and the Reader mode. But I guess if you want to find some minor technicality to bash Apple on, then fine. Just seems a bit childish to me...
"the Install disc that came with it. If you can remember where you put it."
The install disc is in the box your Mac came in.
You did save the box? Of course you did as it increases the price you get when you sell your used Mac.
Only idiots don't save all the Mac packaging.
... but neither "infinitely capacious and reliable hard drive", or other "moving parts with miraculous, never-ending lifespans" are on the list.
And heaven forfend that someone might actually want to upgrade their hard drive at some point in the machine's future. Apple kit tends to have a pretty long lifespan. And surprisingly good resale value too. Which reduces the TCO, incidentally. (As an earlier poster pointed out: only the first Mac is expensive: any subsequent machines you buy are reduced in price by the resale value of its predecessor.)
SIMBL's running just fine here: Safari did moan about Safariblock and refused to load it, but Safari Adblock (which also runs on SIMBL) seems to be perfectly happy. ClickToFlash is also happy in its new home. Between those two, my plug-in needs are currently pretty much met, and I'm really getting a sense of Teh Snappeh™
Until now, Safari plugins have had to rely on using the InputManager framework in OS X. The framework is designed to enable support for alternative text input methods, not as a plugin-architecture.
http://macdaddyworld.com/2007/11/06/theres-something-about-input-managers/
This, along with the use of undocumented (i.e., private) APIs which are **subject to change without notice** are the root cause of the upgrade problems mentioned in the article.
SAFARI 5 OFF TO APPLE'S TRADITIONAL ROUGH START
What rough start? I’ve been using Safari 5 for the day, fairly heavily without any problems.
Oh! This is just the typical Reg anti-Apple/Jobs rant. The headline as bait to distort reality. The Reg often has its own reality distortion field when it comes to Apple
I'm wondering what the fuss is about.
Almost every time a new point release of Firefox comes out there are a bunch of plugins that stop working. Typically anything still being worked on is patched within a month and I can begin looking for alternatives for the remainder after that.
That's just a point release, when there is a major release like this you can pretty well forget about using any plugins for a couple of months.
All we're seeing here is who is pro-active, who is reactive and who's given up.