In October, when Steve Jobs publicly called Google's claims of openness "disingenuous", Android chief Andy Rubin responded with the first tweet of his life:
the definition of open: "mkdir android ; cd android ; repo init -u git://android.git.kernel.org/platform/manifest.git ; repo sync ; make"
In other words, Rubin says open means that you can use a command line to create a directory, download the Android source code, and build your own OS.
By that definition, Honeycomb is not open. Sometimes, Steve Jobs is exactly right. ®
It really is a better antenna and gets better reception, overall, than any previous iPhone. That’s really the hell of this whole goddamn situation. It’s like a two steps forward, one step back design, except maybe more like three steps forward, because this thing is faster at downloading, 10 times faster at uploading, and most importantly is better at not dropping calls with a weak signal.
iPhone 4 has a pentaband antenna/chipset (although the Apple specs page only lists four, the FCC lists five bands), meaning it works not only on the GSM frequencies the earlier iPhones did, but it also now supports 900 MHz UMTS/HSDPA. This increases the utility of the phone by a great deal for many international users, many of whom will now have access to extended 3G networks for the first time with iPhone 4.
The antenna in iPhone 4 also means it's now a true "world phone" -- with access to GSM 3G over different frequencies, iPhone 4 should be able to connect to virtually any GSM 3G network in the world now (with the notable exception of T-Mobile in the US).
It's also likely iPhone 4 will have much better wireless reception than earlier iPhones because of its construction. According to the keynote, the stainless steel side casing functions as part of iPhone 4's antenna.
I have a mobile machine and having it run backups constantly annoyed me. I guess I'll switch over to something like SuperDuper or Backup.
Someone asked how to keep TimeMachine from running all the time. This happens when your backups are slow. So, in case it can help anyone else, here are a couple solutions:
You can edit the plist or grab TimeMachineEditor and drop the frequency down.
However, there's a better way. Make TimeMachine run fast.
Time Machine keeps one copy of every file it's ever seen, creates a new list of pointers to all those original files every time it makes a snapshot backup, and every time it runs, it compares your current computer's latest files against the previous list. Because of this, I've found the best way to keep hourly snapshots snappy is to:
1) In TimeMachine Options, exclude any constantly changing data that you don't really need a backup of. In my case, that's email. I use IMAP, mail is on the server, so I really don't need my local mail getting backed up every hour. This means exclude ~/Library/Mail. I also exclude ~/Downloads because presumably those files are available online, or if I want them, I've copied them somewhere else. Now I'm not wasting backups on .dmg files I'm going to install then delete. Some system files already aren't backed up, but even so I also exclude ~/Library/Caches, and definitely exclude ~/Library/Mirrors so I'm not backing up iDisk.
2) If you run any VMs, consider excluding their directories too, so you don't copy a 16GB VM image every time you change state in Windows. This saves an astonishing amount of backing up if you use Parallels or VMware regularly. Don't forget to back it up manually though.
3) If I make a major overhaul that drastically changes the content of my drive (for example, do something that adds then delete a large number of files), I usually consider wiping and recreating my Time Machine disk so Time Machine is not comparing a clean state against all those now missing changes. The backup checks through both current and past files, so if you deleted a ton of files and you don't need the backups you've made so far, go ahead and start your Time Machine backups over.
When I was backing up Mail and VM images, my backups took longer than an hour, and I hated it.
When I follow these suggestions, then the hourly TimeMachine run—even over the latency of WiFi to a TimeCapsule with its internal drive—is usually only a few seconds, and I don't even notice it.