If you use Twitter like I do, you know of the wealth of options you have to interface with others. From instant messaging to custom built clients, you can find just about anything on the Twitter wiki. I’m not sure if that’s a good thing. Twitter enthusiasts tend to agree on the better client for Mac OS: Twitterrific, while the Microsoft Windows crowd is still looking for a front runner. I’ve used a majority of the clients for Mac OS and I find myself reverting back to either instant messaging or SMS. Recently, I (re)tried a Twitter client called, Snitter.

Snitter stands for “Snook’s Twitter” and it is an Adobe AIR application. Adobe AIR is a cross platform (Mac OS and Windows atm) framework which uses a combination of popular technologies to produce rich applications. Snitter is actually an excellent client. It has great error handling, great features, and extensive customization. I really really like it. There’s just one problem: Adobe AIR. Adobe AIR, like Java, sacrifices resources to give you cross platform capabilities. On Wednesday, I clocked Snitter at 238MB of memory consumption, while Flock was running at 210MB. No way a twitter client should consume more resources than my web browser. If it weren’t for this fact, I’d recommend Snitter hands down over the competition, but since the framework is piggy, I can’t. If you’re willing to sacrifice a good chunk of memory for an excellent Twitter client, give Snitter a try. Otherwise, I’d recommend sticking with instant messaging.

Snitter 0.20

Related posts:

• I’m on Twitter
• Twit-out Preparation: Are you ready?
• Nokia E61 – Pulling My Heart Strings
• 7 Ways to Improve Alert Thingy
• yes you can upgrade the memory