MidKnight Gallery

With a recent announcement by Google, you can almost hear the air getting sucked out of .mac’s sails.

Say what?

OK. .mac is Apple’s much touted, and honestly, underdeveloped mail hosting service/sync service/online disk space/remote access service that was recently rebranded as mobileme/.me. Frankly, it’s a bastard stepchild. While I’ve had legitimate uses for it and it’s premium pricing (just wait, I’ll explain), most users have never needed most of what it offers, or could easily get it for free. The biggest thing going for it lately was .mac-based syncing for the iPhone, that offered a compelling reason to shell out the bucks.

Well, Google is now offering exchange-server based syncing called Mobile Sync that works with a number of smart phones – including the iPhone. With it, you can keep your gmail-based contacts and Google calendars wirelessly synchronized with your iPhone. And it’s free.

OK. It’s hardly the end of the world. There are still a number of advantages that .mac has, but Google sync just made it a lot less compelling.

Pro’s for Google Mobile Sync:

• Easy to share calendars with other people and fairly easy to see other people’s shared calendars as long as they’re on Google. Google calendars has it all over iCal here.
• Reliable. You don’t have to deal with the vagaries of Apple’s built-in syncing services. Google has the server, Google keeps the calendar. Any changes you make to it after using the calDav tools like Calaboration to give you direct access to your Google calendar in iCal will be reflected within minutes no matter where else you look at your calendar. The calendar and contacts are synchronized over the relatively tried and tested (yes, I’m grinding my teeth saying it, but credit where due) Exchange activesync services. Since the current Apple Address Book app in Leopard natively syncs to any specified Google Mail account, this gives you a completely different channel to keep your mail and contacts and calendars synchronized on your phone and desktop. It also makes them available via the web, while letting you use the interface (web or local) that best suits your way of working.

Cons:

• Privacy. Well – there are some who worry about Google and privacy. I understand these concerns, but don’t worry enough to not use them where they’re the best tool for the job.
• Five Calendars synchronized. You can have more than five calendars, but only five of them can be synchronized to your smartphone. I solved this by grouping what used to be separate calendars together.
• Ease of setup. If you have a new computer and iPhone – great. No problem. However, if, like me, you have a bunch of contact and calendar information already, then .mac is still the clear winner here. Between consolidating calendars, backing up data on the phone and the computers, exporting out individual calendars to import into Google cal, importing them, etc… it’s hardly a painless synchronization  or one-click export. If, on the other hand, you already use Google and never used iCal anyway, then you still have the option of viewing the calendars in iCal. This is useful because a lot of programs in OSX are aware of the address book and the iCal calendars.
• .mac plays better with mail programs than GMAIL. Especially the built in Apple Mail.app. Go figure. That said, this is true because Google does a few non-standard things to make tags work within the folder paradigm that most mail programs use.
• Doesn’t replace the “Back to My Mac” functionality. – though as I recall LogMeIn now has a free mac program that allows you to get some of that (remotely controlling your computer) for free.

So… getting all this to work can be a little harder than .mac, and you still don’t get to synch bookmarks, but it’s free, and it works. For people like me who’ve had a .mac address for years, well, we’re not giving it up. At this point though, I can’t really point to mobileme sync as a compelling reason to push .mac/.me/mobileme.

At first glance the two wouldn’t go together. I’m glad to discover I was wrong.

Eifelheim is a book in two ages. A near-future where a historian tries to puzzle out why a town site was abandoned and never resettled, and a small german town in the 1300’s where the local preist is amazed to discover the most unusual pilgrims.

In and about the story, the typical questions are asked and explored about the nature of humanity, as well a few about faith, religion, and the nature of science and research.

I can definitely say I’m glad I read it.

I’ve taken to joking that I love my Macs, but Microsoft does more to give me business… fixing problems.

The latest? Installing an upgrade from the student/teacher version of Office for the Mac to the full version. The installer never asked me for the new license key, which should have been a sign of something going tremendously wrong, but I missed it.

The first sign I caught was not being able to open the existing email libraries. It turns out the S&T version had been updated to 12.1.5, and the version on the installation disc was still 12.0.0, so the libraries could not be opened by the “older” version of Office 2008. Not a huge deal, just run the updates, right?

Well, unless the updates won’t run. I tried running the built-in updater, and downloading the updates separately, but I kept getting the error that there was no software to update, or that the update could not run.

For whatever reason, either the key not being checked against the software version, or the patchers seeing more recent files spread across the computer not affected by installing a fresh copy, would NOT upgrade the older version until I not only uninstalled the application with the built in uninstaller, but deleted all references and preferences in both the system and user directories.

A completely clean install later, and the updates ran, and everything worked. Getting there only wasted five or six hours of working time for two people as well as my time fixing it for a process that should have only taken thirty minutes.

Well. It has now been a whole year since I got my iPhone.

Insofar as changing my life, well, I’m not making millions in Hollywood, and I don’t have hundreds of devoted followers.

All in all, I’d say that’s a good thing.

It definitely has been a boon though. The ease of email, texting, keeping my calendar on me, etc. has made it much easier to keep my life in order. My wife called it the first phone she didn’t want to throw across the room. It definitely is the first phone she knows how to use everything. Of course, I would not be as happy if the iPhone were still stuck with its original capabilities, as the added software has made all the difference in the world. Google maps and street view have helped me get directions and verify them. Facebook has let me keep in touch with friends. Remember the milk has made todo lists that I can keep with me EASY. I can even read ebooks from Baen and other publishers, IM, check bank balances, keep up on Twitter, or write entries like this to my blog. And then there are the games.

All is not perfect. While most places had better coverage under AT&T, my home coverage continues to be flaky at best. It’s an awkward shape for a phone (though no worse than many Blackberries), and sometimes you trigger something you don’t want to because of the touch screen.

But I’m glad I have it.

–fixed some typos due to my fat fingers while punching it in on my iPhone

Well. Some of us already have our kids back in school, and some don’t. Some won’t this year, but the advice here applies to a lot of people wanting to lock down their laptops a little better for public use.

The kind of iPhone app I’ve been waiting for the longest….

One word: Amen

On an iPhone related note, there is now an app in the iPhone app store that allows you to post Worspress-based blog entries and edit them on your iPhone or iPod touch.

One of the new features that has been added that’s a no-brainer in retrospect (though none of my previous phones had it) is an ability to take screenshots of your iPhone screen. This means documenting iPhone features, showing off how cool your game looks, etc. all are much easier to do.

This also makes it very easy to note one thing that many people “know” but don’t give much thought to. If your website is Flash heavy, or worse, almost exclusively Flash, here’s what it looks like to an iPhone:

That little blue building block? That’s the “I don’t know how to play this content” icon where a website decided to have everything Flash-driven.

Yes it’s true that Google has arranged with Adobe to index flash files. This mitigates, but does not eliminate the argument that Flash-heavy content hurts your search rankings, even in Google. Nevertheless, creating Flash-heavy sites, especially sites that have no easy way to bypass the Flash, means that anyone without access to a full desktop is unlikely to dig up any useful information about your company, such as phone numbers to contact you.

Just a thought.

I’m very impressed by what the guys at Google have released so far. They’ve already addressed several obvious issues that made it an intriguing development platform in development, if you’ll pardon the expression, but useless for me. The biggest one is image resizing and manipulation.

Hearing this, I revisited it and am quite impressed. For ajax-based work (like custom coding an editor) it’s more complicated than straightforward PHP/Javascript development for small sites. This is mostly because of the need to tell at least two sets of files what’s handling a request for a web page before you even get to wiring up the python code to the template. What it gives you in return though is an absolutely stunning level of scalability, as well as a very rapid method for prototyping all of your changes.

The remaining headache is the need for some form of version control. You can have different 
“versions” of an app posted, and roll back to a prior version, but there’s no integrated access to a common file repository where people can independently work on different files and see the combined changes before deploying them to the server. Guess I’ll have to figure out how to set up my own repository and how to make it so my fellow developers and I can work on it, along with a workflow that won’t cause headaches in deploying to the Google apps site.