That’s why I decided to try out Tumblr today. Unfortunately, no WordPress importing, no proper exporting, no visible way that it’s getting income (so that I can rest safe knowing that it won’t die on me suddenly one day thanks to going bankrupt or whatever), flexibility is limited by things like no plugins/server-side code etc, and the list goes on.

But I still tried it anyway. Why? Because as Automattic had once on their website… “Blogging is too hard”. For some people, it isn’t a problem at all. But WordPress for me has a ridiculously overloaded interface, and QuickPress is to me a lazy method of simplifying things. In the end, I don’t like navigating through the strangely clean looking bloat that is WordPress.

Tumblr is a dream, in that regard. The dashboard is clean, simple, and amazing. But really, weighing that (and some other advantages) against the downsides, makes me in the end, go back to WordPress.

So, now what? I still haven’t solved my problem. I like the tumblelogging methodology. (so I don’t look like I’m dead, maybe? That’s not necessary, but I digress…) So. Now what? Well, I’m a user of Firefox, and I’ve been using a plugin for it called Echofon. (which I still fondly remember as “Twitterfox”, because it doesn’t sound like it was made up as a corporate cliché) I like Echofon, as it’s faster. I absolutely hate desktop Twitter clients. Sure, it’s still a single click to get into a Twitter interface, but I prefer my minimalism and having some things intertwined in ways that can probably be explained but I can’t.

That gave me motivation to look up a WordPress plugin for Firefox. And I landed on… ScribeFire. I’m quite liking it so far…

Except for its heavy usage of screen space (about half of the browsing area is taken up by it), and the tracking code option it has enabled by default. It’s quite shady, and I don’t like that. But at least you still can turn it off. In any case, I’ll see how this goes.

I’ll give it a 4/5 in my head for now.

A few months back, I made a promise to myself. As a person who liked web design and development and new, shiny things, I should be staying on the cutting edge. That’s what I’ve always been doing these past few years. I jumped to try out the leaked pre-beta of Windows 7, and kept using each of the public betas until release. Things like Ubuntu, web scripts, programs, if I see the term “beta” next to “stable”, I practically always go for beta. Giving back feedback is something I have time for, as well.

Thing is, it’s all and well until things start to break. The recently released jQuery 1.4 rc1 when dropped into some of my projects immediately broke a few of the plugins I depended on. Brilliant!

This applies to other things such as Firefox as well. Add-on developers usually don’t tend to begin adding compatibility to point releases until they’re finalised.

It makes me think.