This week Adobe released the latest version of the Creative Cloud, and converted all Adobe apps to a subscription-only model.
A while back I wrote about how Adobe had lost their way, and while this isn’t a full reversal, Adobe appears to be working hard to provide value in a number of different ways.
Early versions of Creative Cloud were mostly disconnected from the applications themselves, and felt loose and unpolished. This update ties everything together and unifies the experience. I don’t use Adobe’s online storage, but with the addition of version control and support for teams I’m considering it. Also, Creative Cloud subscribers get access to a Typekit account, rounding off a service which is about more than just downloading applications.
There is some discussion about whether the subscription cost provides value over a one time cost, but my current cost for CC access is just $30 - for me it’s hard to quibble at that price.
Looking forward to more progress from Adobe.
It’s hard to deny that Microsoft is struggling to make an impact in the realm of next-gen computing. Only a short time ago I would have typed that gleefully, but not so much these days. Microsoft’s Windows Phone UI is legitimately interesting and as I planned to switch to a new phone, Nokia’s Lumia 920 offers what I consider to be the first real alternative to Apple’s juggernaut iProducts (side note: Android is definitely not for me).
However, my sympathy for Microsoft ended abruptly after several months of trying unsuccessfully to switch to a Windows phone. For some reason, the Lumia is exclusive to a single carrier (AT&T in the States, Rogers in Canada). I won’t switch to Rogers, and there seems to be no legitimate path to buy the Lumia 920 even at full price for use on my network.
I’m sure there was a valid business purpose to the exclusive agreement, but while Microsoft and Nokia are struggling to gain a meaningful foothold, they shut out a customer who was willing to pay full price for a Windows Phone.
iMessage combines two tired but fairly resilient technologies, instant messaging and texting, and combines them in one single, proprietary, magnificently broken system. How does iMessage fail? Let me count the ways..
- Messages bounce with no explanation or obvious reason.
- Messages seem to arrive (or not arrive) at various devices, seemingly at random.
- Messages, and even chunks of conversations arrive at the device/computer but then disappear.
- Messages appear out of chronological order, even on a single device but particularly across multiple devices.
- Messages are incorrectly marked as read or unread, and do not respond to being marked as otherwise.
All of the above have been true, and are getting worse, since the launch of iMessage. What’s more, there are very few troubleshooting techniques - iMessage is a magic black box into which messages enter and are spat out inconsistently if at all.
Interesting find - I’ve long been interested in simple ways to run an AMP (Apache, MySQL, PHP) stack, and the most common option is MAMP (Mac, Apache, MySQL, PHP). I’ve never felt that comfortable with MAMP - it feels heavy and (IMHO) it’s clunky to administer, and you need the paid version to use it fully. In my search for an alternative I discovvered XAMPP - I preferred it, although it’s infrequently updated for Mac, and documentation is light.
A new discovery is AMPPS. It runs on Windows and Mac, is FREE (!) and seems like it strikes the perfect balance between giving you a minimal setup and a comfortable level of security and configurability. Rather than aim to provide GUI configuration, it simply links you directly to the .conf and .ini files - this looks great to me, since I can do the same level of tinkering on my mobile dev system as I can on my web server.
Eventually I’ll get round to writing up my workflow for building websites and Wordpress themes.
I’ve been running a Mac Mini as a home server for a while, with a few simple tasks running. I’ve always wanted to fiddle with server setup a little more, but documentation from Apple and on the web in general can be muddled. I began with this great article from Hoffman Labs which does a great job of explaining some of the intricacies of DNS, but I had some very specific requirements, and the article didn’t cover all of them.
This is a welcome announcement - Parallels has released two iPhone apps to monitor and manage your Plesk configuration.
You’ll need to update to the latest version of Plesk (10.4.4), but the apps are worth the time and effort for me.
I’ve had some pretty awful experiences with registrars and hosting, but one recent experience was so awful, so time consuming, so painful for everyone involved it almost beggars belief.
In terms of domain transfer, it doesn’t get more simple. With access to both the outgoing and incoming registrar, I should have been able to perform all necessary tasks within a day, with the transfer completing 5 – 7 days after.
I logged into Dreamhost, the outgoing registrar, ensured that the WHOIS information was correct and unlocked the domain for transfer. I also double-checked that I was able to access the authorization code.
At the incoming registrar, MyDomain.com, I initiated the transfer. I received a notification later that day that the domain could not be transferred with the error ‘ADMIN_EMAIL_FAIL’.
Painful experience has taught me that at this point, the best course of action is to check the WHOIS data for the domain, because occasionally the registrar’s record differs from the official record. Sure enough, at http://whois.cira.ca the only information shown was the nameservers, indicating that some setting somewhere was preventing the information from being shown, and most likely wasn’t available to the incoming registrar.
Below is the full transcript of the conversation with Dreamhost support. It’s lengthy, boring and repetitive, but maybe someone within Dreamhost will see it.