safari

If you are on the latest version of OS-X Leopard (10.5.6) and Safari (3.2.1) you most probably have encountered the infamous Safari Can Not Keep Cookies problem. You can see from the discussions on Apple.com threads that a lot of people are affected by it, it has been going on for weeks now and there is still no resolution or even acknowledgment from Apple.

This is wrong on many levels. First off - managing cookies properly is a basic feature of a web browser and it's embarrassing to not get it right. Granted everybody makes mistakes, but after so many people are affected, it's reported to Apple Software Support line, it's extensively discussed on apple.com threads - how come nothing is done? How can it go on for so long? After all, Apple does have one of the best software engineering teams in the entire industry. Why is nobody taking any action?

Last, but not least - are Apple employees even using their own software? :) I mean, we are not talking about some weird combination of versions and setups - latest OS and latest browser update do not work! Even if they care little about the end-users, how come this does not affect them? What's Steve Jobs using? A Windows? :-)

Something's rotten in the state of Cupertino!

Cooliris is one of these new gadgets that sound cool in somebody's blog review, but do not live up to an expectation when actually used. Let alone that it is not nearly as useful as it claims to be, Cooliris has been reported to significantly slow down Safari on Macs. Specifically - when viewing FLASH videos like on YouTube. These fellas must have done something terribly wrong.

In any case, the real sad part is - they don't have any human way of uninstalling it. So here is a quick tutorial of how to remove this weed from your computer and let your Safari breath again:

• Close Safari
• Trash the Cooliris Previews folder found in $LIBRARY/InputManagers/)
• Trash the cooliris' .plugin file found in $LIBRARY/Internet Plugins

Depending on whether you installed Cooliris for just your user or system-wide, substitute $LIBRARY with /Users//Library or /System/Library.

Hope this works for you, too.

The confusion is over - Apple revealed the secrets of creating slick iPhone applications.

When Apple announced iPhone in January, this year, the shocking news and the source of much speculation became the alleged lack of third-party application support. An intelligent cellphone without Java/J2ME was so unusual that for a long while it gave Apple-haters a thing to wave in front of everybody's face and left Apple-lovers confused and curious for what it really meant.

The first clarification came during the Steve Jobs's WWDC keynote on June 11th and once again proved how risky it is for mediocre minds to challenge the design decisions of the Cupertino-based centre of innovation excellence. The message was quite short and ambiguous, yet loud and telling: the future of the mobile applications, as Apple saw it, were Web applications.

Steve Jobs announced the availability of Safari 3.0 Public Beta during yesterday's WWDC Keynote. For audience at large the biggest news about the release was that it is now available on Windows, as well. However, apparently there is a "hidden" (well, unpublicized) new feature that is just as exciting for Mac geeks like moi - Web Inpsector.

Web Inspector is a context menu-activated DOM analyzer a-la FireBug for Firefox. This thing is sweet (!) and will make Safari troubleshooting much nicer, from now on.

Thanks, Apple! Well done.