From TFA: "When clocks struck midnight on January 1st and the dreaded Y2K bug turned out to be nothing but a mild irritant, it proved once again that the experts often don't know what the heck they're talking about."

Well, that kinda hurts.

I was responsible for a newspaper ordering system that definitely would have stopped processing orders in 2000. Cost quite a number of man hours. The majority of the Y2K my team had to solve weren't for the year 2000 but for passing into the year 1999 because many ordering systems had stupid (year+1) counters internally. It was a very stressful period and I very happy it went the way it did without major disasters.

The experts that didn't (and don't) know what they are talking about are the ones thinking you can upper-limit a year counter at 1999 (or 2039).

Gilmoure's article almost feels like it was posted just for the heck of it. Or he has very particular designer friends.

How could a switch to some open source alternatives be in anyway better than running a "not officially supported but otherwise proven" version? Every existing file would have to be converted, there would be many conversion issues. If the design friends are working for a design studio it would be MUCH cheaper to just upgrade to CS4. Or to stay with Mac OS X 10.5 for the time being.

Anybody that's making a living on production work using computers should stay away from version .0 upgrades anyhow.

Next time in a forum: "I've voluntarily upgraded to Mac OS X 10.6 and now my Photoshop documents are corrupted. All my customers are angry and I'm loosing a lot of money and all my customers go somewhere else. Sue Apple!"...

If you install a lot of non-Apple stuff you have to know how to use ssh/scp/rsync if you want to keep all your non-Apple-application data over upgrades. I usually make a rsync backup of my phone before I upgrade so that I can rsync stuff back afterwards. Keeping your packages is reatively easy, just list the ones you installed before upgrading (dbkg -l) and use apt-get to re-install them after upgrading. With the latest Cydia incarnation you have to use Cydia's GUI app to install apt-get after you upgrade. The average user would probably just use Cydia's GUI to install the three or so Cydia apps that got lost during the upgrade. And please change your ssh password (default = well known = alpine) if you leave ssh on. For both users (mobile, root).

That's not quite right. Firstly jailbreaking has almost nohing to do with the ability to make phone calls. Secondly the cat-and-mouse thing is not your call, you simply need to wait a bit longer before you upgrade your phone to the lastest and greatest. And thirdly when you acidentally do upgrade "the official Apple way" the jailbreak is gone and you are left with a perfectly working non jailbroken phone.

Unlocking however is something else entirely.

Oh apparently they already did. As of 30-7 "GV Mobile" version 1.2.2 is available in the ModMyi repository in Cydia for free. See http://www.iphonefootprint.com/2009/07/gv-mobile-and-other-google-voice-apps-goes-underground-for-jailbroken-iphone-users/. Official word from Sean Kovacs can be read here: http://www.seankovacs.com/index.php/2009/07/wow/.

There is a side-effect to jailbreaking that's worrying Apple. Jailbreaking disables application signing. A jailbroken iPhone will run any software you compile yourself but it also runs any official AppStore packages you care to install on it. In other words apart from opening up the phone it also enables software piracy. And that's not a good thing for (commercial) developers IMO.

Maybe Google should distribute Latitude using Cydia (APT for iPhone, http://en.wikipedia.org/wiki/Cydia_(application)). This would provide everything it needs including background tasks and maybe, just maybe, it would be a wakeup call for Apple...

OR they buy a legitimate $1 gift certificate and use its number to create a $200 gift certificate. I can not imagine that they would make the mistake of not linking the part coding for the amount to the part making up the unique identifier. But who knows...

Only 30GB? :-)

No I don't sync the Music library, I sync iTunes' settings (iTunes Library; Album Artwork/; iTunes Library Genius.itdb; iTunes Music Library.xml ;iTunes Music; iTunes Library Extras.itdb), as I said the Music library itself is on a common share.

To play the same music from outside your local subnet there are all sort of possibilities. For instance there's MyTunesRSS which let you play your music from any web browser supporting Flash (with a little bit of Apache configuration all you need is port 80 so it works almost everywhere); then there's a simple hack where you locally copy all traffic over TCP port to another TCP port and inject the proper mDNS stuff in a computer outside of your network and play your music anywhere using iTunes itself; or simply use Simplify Media and play your enitire music collection anywhere even using an iPhone over 3G in your car. And that's just three examples.

If you think even a little bit out of the box a lot of cool stuff is possible. I can't understand why all these Slashdot unix geeks are suddenly so limited and "locked up" as soon as they hear the word Apple. Behind that "pretty ui" there's another environment where a lot of nice stuff is possible.