Tag Archives: private

Mike Ash on private APIs

Mike Ash has been rocking with his weekly Friday Q&As. From the “latest about using private APIs”:http://www.mikeash.com/?page=pyblog/friday-qa-2009-01-02.html:

“Remember that the cost is not just to you, but to your users. If you’re really unlucky the break will be so bad that it’s not even obvious that it’s your fault, and they’ll figure it out only after much head-scratching. Once they do figure it out, they will hate you if your fix doesn’t come really fast.”

My new app (not officially announced yet — more later) currently uses Quick Look as a significant part of the user interface. Quick Look is a private API on 10.5, but my hope was that surely it would be made public by 10.6. If I coded correctly for both cases (I have a 10.6 seed running here I can test against), then I could safely release the product and be reasonably certain that nothing would be break.

I’m now rethinking that, both because it looks increasingly like Quick Look will remain a private API even in Snow Leopard, and because I’ve gotten feedback that it’s not a perfect fit for how I’m using it anyway. At the very least I will turn Quick Look into a secondary option, something that wouldn’t be missed if it went away, and roll my own preview UI to be the default.

How I use Twitter

“Twiterrific 3.0”:http://iconfactory.com/home/permalink/1887 is out, with a new price of $15 or free to use with ads. The ads are very effective and difficult to ignore, but really they don’t take anything away from the Twitter experience. The new version is great, though, and I’ll be sending my $15 to Icon Factory sometime in the next few days. “As Fraser Speirs said”:http://speirs.org/2007/11/02/twitterrific-3/, it’s a small price to pay to be connected to friends and colleagues.

I post to Twitter much more often than I blog now, and I think I owe some of my followers an explanation. I made a rule for myself early on to only follow people who I have met in real life. I’ve only made a couple exceptions to this, and none recently. It keeps the flow of tweets easier to manage and relevant.

So if you follow me on Twitter and wonder why I don’t return the favor, that is why. You probably have interesting things to say, so say hi to me at some future conference so I can add you to my list. I’ve actually been thinking about taking it one step further and protecting updates, because I tend to post about what (to this blog) have been traditionally private matters. Jury is still out on that decision.

The following numbers are interesting, though. I only do very basic Mint stats for this blog (I just care about referrers, not number of readers), but it does make me wonder how many people read this blog. If you’re reading this, add a comment to this post. (Haha, gotcha! I don’t have comments.)