> Enjoy the bleeding edge on that 27" iMac!

I try not to jump into the vanguard of the shock troops of consumerism to be mown down by experimental hardware designs. Just a general policy I have. Because 'bleeding' and 'edge' are two words that describe only hurt — is there really an upside to this concept? If there is, no one ever seems to just come out and nail it. Having the latest, most crappily engineered and untested thing is a luxury which, however questionable, appears to just go without saying on this world.

So, I've advised against buying the new 27" iMac, which simultaneously violates two of my cardinal rules of Earthly computer hardware purchase: Never buy the first available prototype of a new enclosure; and, Never buy the first available installation of a next-generation CPU in an old enclosure. Manufacturers, including Apple (some might even say especially Apple) hew pretty close to the heat tolerances of these components they use, in the rush to achieve their latest avant-garde design. Apple cuts engineering corners, and it affects first-generation product reliability, as we've seen with the capacitor problem in early, large white iMacs, and now the cracked or DOA Intel Core i7-based 27" iMacs.

Lest anyone think this is a new development, I should point that the very first Macintosh ever invented didn't even have an internal fan, despite being offered in an almost unprecedently small, and thus hot, enclosure (for 1984). Unsurprisingly, the first generations of Macs had a habit of frying their own power supplies after a few years, and then burning up the replacements, a few years after that. The 'novel' idea of fan-based cooling wasn't welcomed to the Macintosh until 1987, with the Macintosh SE.

> Unzip iWork documents

Exactly as it reads above — if you want to poke around inside an iWork document and examine its structure (which is XML-based), all you have to do it unzip it.

> Check apps for Snow Leopard compatibility

The Unofficial Apple Weblog pointed me to SnowChecker, which will detect all of your apps and compare them with an online compatibility database. It doesn't really detect them all — it didn't pick up on any Adobe apps, for example — but for a cautious upgrade-shy fellow like myself it's a good indicator of the current state of things.

My verdict: this cat is not ready for primetime yet. Which means it isn't ready for my Mac.

> Get info for multiple files in one window

This is mostly useful for finding out how much disk space is taken up by several different files, without putting them in a folder together or moving them around.

Select the files in the Finder, then, instead of Command-I (Get Info), use Control-Command-I (Get Summary Info).

> Fail to use the new iMac as a TV

In case you heard about the fact that Apple's new 27" iMac can also double as an external monitor, and you were getting excited about all the different kinds of devices you can attach to this thing — don't. The iMac will only accept DisplayPort input. This 'feature' is designed not for your convenience, but to promote an Apple-favoured standard with little prior presence in the marketplace. DisplayPort might eventually achieve wide adoption, but by the time this feature becomes generally useful, your iMac will almost certainly be obsolete.

> Avoid guest accounts on Snow Leopard

Using guest accounts on Snow Leopard could cause your entire main account to be wiped. That's right — wiped. Still feel comfortable out there on the bleeding edge?

> Bank on Apple's nonexistent credibility

Erm. Something tells me that Apple — a company whose name is becoming increasingly synonymous with corporate censorship and interference with interoperability for user control — is unlikely to win any kind of widespread consumer support for its new universal connection standard. Rather, the best survival chance for any new interoperability protocol would be if it weren't mentioned in the same breath with the name of the most notoriously willful foe of interoperability of the 21st Century.

> Prolong lithium-based battery life

Lithium-ion and lithium-polymer batteries have a few key differences, according to this Battery University guide, but the main danger to laptop battery remains the same.

With the nickel-cadmium or nickel-metal-hydride batteries common in the 90s, you would need to discharge fully quite frequently to avoid the 'memory effect', which should be called the 'forgetfulness effect', because it happens when batteries forget that yes, they actually do have more power left, and quit prematurely, thinking they're out of power. That's an act of forgetting if I've ever seen one, but with lithium-ion and lithium-polymer, you don't have to worry about it; frequent shallow charges are not only safe but less stressful and healthier for the battery. You only have to discharge fully maybe once a month and that's only to give the software gauge a chance to recalibrate to the size of a full charge.

However, this is all scribbling in the margins of battery life. Charge or discharge frequency were never really the main thing killing laptop batteries. From what I have witnessed, people have just been killing their batteries by leaving the mains adapter plugged in way too long, sometimes for days. I've seen some random internetling claims that lithium batteries can be safely left docked indefinitely, but the Battery Guide article says nuts to that: forcing a battery to remain in a state of full charge with constant heat applied for an indefinite period is just a great way to age your battery chemistry at a far accelerated rate — even lithium.

Bottom line: you can read that whole article, or you can just not work with your laptop plugged in unless your battery actually needs charging. This single factor explains most of the differences I have observed between the battery life of different laptops in different environments.

> List what's been removed from Snow Leopard

An informal list has formed at Waffle [via Daring Fireball]. The knifing of PowerPC support was widely expected, but the dropped creator code adherence is going to spark a bunch of people to falsely believe that their system can no longer open their oldest files anymore, when the truth is that it has merely forgotton how to figure out which app to open them with.

I can understand clearing out the cruft, but adhering to creator codes made the system more intelligent about how to open your legacy files, so that really wasn't cruft at all, was it?

[ UPDATE: Looks like I'm not the only one who was shocked at the braindeadness of the creator code move: see more details and complaints about this issue here and here. ]

> Solve Exchange/iPhone bug by turning off security

Nope. Not kidding. That really is Apple's official, recommended solution to the recently reported 'surprise policy enforcement' that results in a broken Exchange functionality for any iPhone that is upgraded to firmware 3.1.

Apple doesn't let you downgrade your phone, so if you leapt early, you got burned — big-time.

> Fiddle endlessly with Photoshop CS4

If you're feeling incredibly obsessive about small gains, take a look at this beyond-comprehensive list of ways to use Photoshop CS4 at its very, absolutely fastest. [via Daring Fireball]

The simplest tip on that list is more likely to make a perceptible difference for the average user than all of the others, combined:

"Photoshop requires at least 2 GB of free hard-disk space, but more is recommended. The OS volume should contain at least 20 GB of free space to ensure that the virtual memory system has plenty of available hard disk space."

> Launch any app from the keyboard in Snow Leopard

Never have looked too kindly on increasing my third-party background app load (a very risky category), just to get more keyboard shortcuts in OS X. So, I'm very much looking forward to assigning keyboard shortcuts to launch apps, natively in 10.6 (via macosxhints.com); at least, whenever I eventually, cautiously, pull the trigger and actually switch to Snow Leopard!

Which is something I definitely recommend you avoid, until at least the third 'point update'. Rather than jump into bed immediately with all four big Apple cats (Jaguar, Panther, Tiger, and Leopard), I hung back, watched and waited, until versions 10.2.3, 10.3.4, 10.4.4, and 10.5.3, respectively, to finally do the deeds.

You can ascribe my caution to the ridiculous-but-undeniable fact that it takes this planet at least three attempts to get any new computer engineering to work in such a manner that nobody will need to pay a huge upgrade tax in the time and energy spent identifying mysterious new bugs.

Refusal to participate directly in the bleeding edge treadmill is definitely the way to go. If you have trouble letting go of the immediacy of it all, repeat after me:

"An operating system is a serious piece of engineering. Not a fashion accessory. An operating system is a serious piece of engineering. Not a fash—"

etc.

Restore SMS history from one phone to another

I haven't upgraded my iPhone yet to 3.0. I suppose when I do, I'll have to decide whether to attempt to save my SMS history.

(I really must find a quicker, easier way to post links to this blog, probably involving removing this mandatory 'Read on' custome code I appear to have added at some point.)

iPhone 3.0 Push Destroys Battery Life?

Yes, according to french news site Hardmac.com: "Some users have been complaining that the battery life of their iPhone 3G was dramatically reduced following installation of iPhone OS 3.0. It seems that the firmware is draining more resources when the Push option is activated." Although, according to the Apple Discussion Forums, all that may be needed is a reboot and possibly recreating your push email accounts, and your former battery life can be recovered.

(Drain the battery at least once fully, too.)