Moving my blog to Ghost

I haven't been blogging regularly. I have a litany of excuses, but one I wanted to eliminate was dealing with WordPress.

It all started with Medium

Medium is a relatively new lightweight blogging service created by Twitter co-founder Evan Williams. I'd been using (some would say avoiding) WordPress for some years now, and the thought of something simpler caught my attention.

Medium is simple. I tried it. I like it. I can't use it:

  • It's very aggressive with formatting pasted text in code blocks. It quietly changes normal double quotes into pretty matched (and completely un-usable) double quote characters, among other things. This would make adding usable source code examples tedious and potentially error-prone.

  • It funnels my readers to, well, other writers. I got you to read my blog, and I want you to read a little more before you fly off to someone else who is being promoted by


Mind the (1.5 year) gap

Has it really been over a year and a half since I blogged anything? Is blogging dead, as some bloggers are saying? Not really. Have I been too absorbed in work to write anything? Definitely. Hell, just ask Estelle Weyl, who I left hanging on co-authoring a sweet O'Reilly book (proof that I don't always make lucid decisions about priorities in my life).

I can't say that the past year and a half has been very productive. I got caught up in the dramatic crash of Palm and webOS followed by the amazing relaunch attempt of BlackBerry only to find myself adrift most of 2013. Now I'm nearly into 2014 asking myself where the time went.

Life is truly short. I always "knew" this, but these days I know it. I've got things to do before I'm done.


Leaving webOS, but not the Web

While at Palm and HP, I made it my mission to evangelize HTML5 app development both inside and outside our company. The very core of the webOS value proposition was the web. In webOS, mobile websites, native and web-based apps lived together in a “zen-like” harmony.

At least, that was the theory. In my two years there, I watched webOS slip from a leader in mobile web to a distant follower. I won’t elaborate much on the internal hows and whys (frankly, I doubt I even have the full story anyway), but the simple fact was I had a dramatic drop in confidence in our ability to stay relevant. All the drama in the news didn’t help, and neither did the mighty layoff hammer which eventually swung down on myself and more than half of the remaining staff.

I’ve had a couple months to relax, decompress, and


Urgent Call to Inaction from the W3C

Rarely do I find a need to call out the W3C folks (or anyone, for that matter), but the recent post by Daniel Glazman (@glazou), co-chair of the W3C CSS working group, pushed me over the edge.

In his article, he calls for everyone to, get this, stop using -webkit in their sites. He equates webkit, now a popular engine for most new mobile browsers, to IE6. Moreover, he calls it a “threat to the open web”.


This from the group responsible for years of delays in approving standards? Remember, these are the fine folks who for the past three years have cautioned web developers from using HTML5 (a term used a bit liberally to also include new CSS3, video, local storage, web sockets and other goodies) because they’re still working on drafts for it. Take the canvas tag, a webkit mainstay since 2005, which is still a


JavaScript Library vs. App Framework

Really? There’s a fresh debate raging in the JavaScript community. The battle lines are drawn between those who like all-in-one solutions for app development, and those who prefer to assemble the pieces themselves. Really, the fight is more between those who make these things, not those who use them.

A site for the little libraries

The recent ugliness was sparked by, a small project which aims to list some of the more useful tiny (5K or less) code libraries out in the wild.

Then the flames started spewing over Twitter. The brunt of the griping was focused on @thomasfuchs (of and zepto.js fame) and @ded (ender.js and about 100 other handy things). Arguments generally centered around the size limit (5K): “that’s so arbitrary, why can’t my lib get listed too” (generally followed by much wailing and gnashing of teeth).