OSX as a Ruby on Rails dev environment: Package Managers

A lot of Rails developers like to use OSX as their development platform. Although everybody hosts Rails apps on Linux (or Solaris under duress) lots of people love OSX for its productivity, clean interface, and most importantly, its typography.

However, as some have noted, setting up Rails on a mac is hardly a frictionless process. Unlike Linux distros, OSX has no built-in package manager; you get your version of OSX and you get your patches and you'd better like what you get, because every app is going to be updated when Apple or the vendor feel like updating it. This is the same as the Windows world, and it's ugly.

So a couple of efforts have stepped in to fill this void: MacPorts and Homebrew. Neither of these is going to feel like a complete solution if you're used to a package manager like APT or YUM, but they do at least automate the installation process for various open source packages. After all, when you want wget there's no reason you should have to find the website.

I'll start with MacPorts since that came first. MacPorts was inspired by BSD Ports; it is built in Tcl and C and contains a very complete set of available packages. It is quite popular and is the venerable incumbent. And personally, I hate it. I've had my OSX install ruined twice while using MacPorts, just by installing system updates; although I obviously did something wrong, it just isn't a robust solution. If MacPorts is the solution, I don't want to hear the question.

Another alternative is Homebrew, new Ruby-based system developed on Github. It has been around for less than two years, and it's a very active project with a lot of contributors. It stresses extensibility, and lots of recipes have been written to support various packages - predictably, those most popular with Rails developers. Although I don't think it solves the brittleness problem MacPorts suffers (it doesn't address operating system component and library version dependency issues) it is very actively developed, focused on the Rails world, and easily customizable to meet individual needs.

So, although you're probably not going to get set up with a Rails development environment with OSX as quickly as you would on Ubuntu (despite Ruby being included in Xcode), there are good solutions to keep you from pulling your hair all the way out. Which will bring you to the point where you can enjoy and appreciate the kerning on the fonts in TextMate as you write your Rails code.

Adobe Flash: Just because Steve Jobs says it's bad doesn't mean it's good

Steve Jobs' self-serving Thoughts on Flash were controversial to say the least. Yes, he was hypocritical and self-serving (as usual), but he certainly wasn't wrong.

Adobe wants everyone to treat Flash as if it is an open standard, but they haven't made it open source. They made some parts of it open source, but not the parts that matter - and as a result, developers are constantly left wondering which platforms are going to work.



As a friend said, "Apple seems just as evil as Microsoft, just not as
successful. And Jobs seems even more evil than Bill Gates. Certainly
a bigger bastard." I totally question Steve Jobs' motives in wanting to crush Flash, but I don't think Adobe deserves a great deal of sympathy.

Will HTML5 make app stores obsolete? Don't count on it.

HTML5 is a lovely platform for cross-device development. Basically, it's the only game going forward. But it's really not an answer for building a great app for a given platform. Apple is talking up HTML5 in order to combat Flash, but it's just talking about web sites, not apps. HTML5 will rule the [moribund] desktop, but for mobile devices I think it has major challenges.

HTML5 does not get the same level of access to the device that you need to build a rich experience.

• Integration with the contact list (is there anything really more important?)
• Access to phone status, history and actions
• Camera(s), proximity sensor(s), microphone(s), accelerometer, compass, gyroscope, multi-touch, speakers, etc (and a lot more to come)
• Local storage, access to SD-card files, application backup and restore
• Native configuration and management interfaces (sync, preferences, phone migration, privacy, network gsm-vs-wifi, etc)
• ... drumroll please: the app stores. This is the channel for getting apps for these devices. Otherwise they have to find your website somehow.

HTML5 apps will be good enough in some cases for all devices, but they'll always be step-children to the native environment. You could argue that we just don't care about the weird sensors and whatever else HTML5 doesn't give us access to. I disagree: the really useful apps for mobile platforms will take full advantage of these features, recording and correlating all sorts of information and drawing conclusions from it - where you are, where your customers are, when you're together, what you're carrying with you, how your spouses are getting along, what you've sold them, transcripts of your conversations, your body temperature, what they've bought recently, voice stress analysis, who else is around, what's mouldering in their warehouse, and what expression is on your face. Science fictional? Sure. "The future is already here, it's just not evenly distributed." Mobile technology is going to level the playing field for these kinds of intelligent applications.

HTML5 will continue to evolve and will slowly add access to mobile functionality common to all devices, in a lowest-common-denominator way. The fact that Webkit will be on Blackberry by the end of the year makes HTML5 a cross-browser contender - it will lock up the entire mobile landscape, making cross-platform browser apps even easier. But so far, geolocation is one of the few things that work cross platform. The full list of things above will come over Steve Jobs' dead body. [I'm only half-joking.] PhoneGap is the only cross-platform development environment that currently has any viability at all, and it's risky because Apple routinely rejects PhoneGap-based apps; although they're written in JavaScript which is technically allowed, Apple takes a dim view of anything not *originally* written in Objective C. I don't expect Apple to be changing direction and opening up their platform and their store. If RIM survives [fat chance] its app store may go in a different direction - but I'm not holding my breath: RIM is completely beholden to [evil] carriers.

The app stores are large and getting crowded. But the publishers, labels, studios and carriers are in bed with the Google and Apple markets, and they have real legs. The markets are evolving extremely fast, especially Google's (which is moving into music and movies, and even has meta-markets like AppBrain) and Apple is s-l-o-w-l-y migrating to a non-desktop iTunes store. The smartphone market is exploding, and every one of these devices has an icon on the front screen for the app store. I don't expect these stores to go away any time this decade - there's just too much money to be made.

Why I don't recommend the iPhone 3G

^{backup battery}

I've had the iPhone 3G for a couple of weeks, and although I think it's revolutionary, fantastic, useful, blah-blah-blah, poor battery life is its fatal flaw. For most people, a phone is a phone first and foremost, and other uses are secondary. I know I'm tethered to the internet in general, and email in particular, but a phone has to function as a phone, or it fails. To function as a phone, it has to hold a charge for at least 24 hours under light usage, and the iPhone does not.

This is fixable through software. By being extremely careful about how I turn on 3G and WiFi functionality I can make it work reliably through the day without charging more than once. But I shouldn't have to exercise extreme caution and constantly massage settings to make sure the battery doesn't discharge in bare hours: it is a computer and it should take care of it for me. This is not the traveling salesman problem, it's easy: if the screen is off I'm not using it and I don't need the 3G network, so stop trying to nuke my balls.

I don't know when Apple is going to clean up this mess, but I hope it will be within a few months. Without this fix the iPhone cannot be successful, and I totally want the iPhone to succeed. I've helpfully supplied Apple with a bug report on this just in case they haven't read a newspaper, blog, or spoken to a single sentient being who's used the device. Those of us who have it are doing everything short of implanting a car battery to keep these things running: extra charging cables everywhere, car chargers, and even expensive portable battery packs. Without a fix, this is a failed phone.

Solutions to the iPhone 3G energy crisis

I have the new iPhone 3G, and it is wonderful in so many ways: fast Internet, great mail integration, revolutionary app store, global reach of distribution, amazing polish... but. But.

This has been said a jazillion trillion quadrillion times already on every blog, tweet, IM, and stone engraving in the past forty days, but I've got to say it too: the iPhone 3G's battery performance sucks. It really, really does. Activating the 3G network means that the battery drains in a matter of hours, and even without it turned on it barely makes it through a 24-hour period without running out of juice. It is a power hog, 3G or no 3G, plain and simple. A single charging cable is not enough, because if you leave it at home, you'll need it at work, and vice-versa.

But I'm not just bitching, no, I'm a man of action, and I'm proposing real solutions for the energy crisis with the iPhone 3G. Below are my practical proposals for powering your iPhone 3G while you're on the go.

Miniature nuclear reactor small hydroelectric facility space-based solar array with microwave power transmission

mule team and hand-wired dynamo coal-burning steam turbine diet Coke and Mentos

Yes, someday soon Apple will release a firmware update that lets you turn 3G on and off in less than eight steps. Heck, they might even go buck wild and have it automatically switch to 3G when the bandwidth is needed, and back to Edge when not. (Crazy talk, I know!) But until that fine day, use the handy hints above to keep your iPhone running during that extended period while you walk from your house to your car.

PayPal iPhone app fails

PayPal iPhone fail
Originally uploaded by celeduc

I tried to install the PayPal iPhone application on my iPhone 3G, and it failed. An unknown error occurred (0xE8000022). Whoops!

This seems to work for other people. Maybe it doesn't like Canadians? I would think even PayPal could come up with a better way of snubbing us, if that's the case.

---

Update: as much as I'd like to blame PayPal for this, it appears to be a common problem with iTunes synchronization. So then I have a question for Apple: if this is happening so much, why is it an unknown error?

Mac OSX is way better than Windows, but unfortunately Microsoft sets the bar pretty low. OSX winning against Windows is like a drunken Björn Borg winning at tennis against a comatose chimp.