Conflicting Plugins
Oct 15, 06:41 am
It’s bound to happen. Several plugin developers, all working with their own goals in mind, and no official plugin API to follow. That’s the current state of extensions for Safari, and sooner or later, two or more are going to conflict.
Recently, Safari performance had become really intolerable. Doing anything took so long that I took time out and used Camino for a while. The speed was a huge relief, and for a while I left Safari in the background. One thing drew me back though – SafariStand and those lovely Omniweb style tabs – my favourite tab system.
The action I took was this – I removed all my plugins, and left myself with the 2 that I felt I needed the most. I decided on Saft and SafariStand, and now it all feels back to normal. My theory is that WebDevAdditions wasn’t playing nicely, which is a shame, but its not as high a priority as the other two.
Have you had to do this? Let me know what you’re left with…
Posted by Jon Hicks
now, with saft and safari stand everything is almost back to normal. few rss-related crashes.
ciao