Already I have noticed some major improvements of using Tumblr over WordPress. For the past 6 months I switched from a self-hosted WordPress.org solution to WordPress.com as a cost reducing way of having a blog. Owning my content wasn’t as important anymore in the age of XML.
From a pure cost reduction point of view. I succeeded. I went from paying almost $100 a year to about $25 a year. WordPress.com however charges for domain mapping whereas Tumblr does not. So by moving to Tumblr I saved another $12 a year.
I will be transferring my domain to a different registrar once my BlueHost contract expires (BlueHost domain registration is free as long as you pay the monthly hosting fee, and the contract is 2 years @ $7.99/month or 3 years @ $6.99/month). This way in the end I will be paying $9.99 a year, using name.com as the registrar. For the first year it will be even cheaper because the transfer is only $7.99 and comes with a free 1 year extension. Kind of a way of attracting new customers with existing domains.
The way WordPress.com handles domain mapping and Tumblr is a little different. WordPress wants you to point the DNS servers directly to theirs. Hence you forfeit DNS control, any subdomains you want to use are out of question. For some people it’s okay, but for many others it is very limiting. If someone wants to use any subdomains and point them at a different service, they’re SOL.
Tumblr just wants you to change the A mapping to their hosting IP. It can be done in any form you wish. Whether using the root of your domain, or pointing a subdomain, the user has a choice.
The obvious use of having your own DNS control is to map your own subdomains for Google Apps services (mail.name.com pointing at ghs.google.com, etc). Google’s new implementation of Google Apps account’s integration with the rest of Google services makes this trivial however.
So what will I be doing with this new recovered ability? Well I was thinking of getting a prepaid hosting service and pointing it at a subdomain. Using it for development work and other small projects when I need to. Here’s to hoping NearlyFreeSpeech or a similar prepaid service to support Ruby on Rails or Django in the future.
I’m sure I will discover new things about Tumblr that I didn’t know about now that I’ve made the switch. Hopefully the move wasn’t in vain (it was a painful migration process that involved using PHP scripts and truncating WordPress XML exports). I will write how I migrated in a future post!