Tristan O’Tierney | Mac Geek

I know Wil Shipley talked about this awhile back (hell if I can find the post though) but it bothers me often enough to bring the discussion back up — Why don’t we have more Cocoa libraries for C based stuff in Mac OS X? Everytime some unfortunate functionality requires me to link in some archaic Carbon or C based Mac OS X library I cringe. My first attempt is to check CocoaDev or CocoaBuilder praying that someone’s been annoyed enough by the lack of a Cocoa wrapper for their favorite library to go write one, and maybe the license is something I can use freely. Sometimes I get lucky, sometimes I come up short. What does bother me is I feel like sourceforge, freshmeat, etc just aren’t quite the places to go for this sort of code and I think other mac devs feel the same way. We need something like macosxforge where Cocoa devs can go, without going on a google hunt, to find native cocoa libraries that take the headache out of dealing with this relic of Mac OS 9 style coding. Anyone with me?

I’m not sure who reads my blog, but for those interested — I’ve accepted a job with the Safari UI team and will be starting in mid-May! I’m totally stoked and think this will be wild ride. As a lot of my friends knew I had a back-and-forth debate between VMWare and Apple and couldn’t decide on one or the other for any substantial length of time. My decision rested on the fact that, right now, I could probably make a bigger dent in the world through an application as universal as Safari than VMWare Fusion. Well without going into too much of a monologue that’s that.