Tag: <span>Six Apart</span>

In case you hadn’t noticed I’ve not really had the motivation to post here everyday. I mean, I still feel that I should (4 years of habit is hard to break, just ask Nadia, BB’s very own nicotine bitch) but it’s a bit of a struggle sometimes. Hiatus, shmatus though. You’ll just have to suffer with me.

I should mention the New Moveable Type licensing – given the amount of column inches (literally!) this was given when they first announced the prices I think it’s only fair to mention this. Seems like the good folks at Six Apart are listening and have changed the prices. I won’t say that they maybe should’ve done some of this ‘negotiating’ with, say, the BETA testers… oops, I just did.

Ohh yes, and it’s Father’s Day on Sunday. What the hell do you get for the Dad who has everything? Dad, feel free to chip in here too!

Comments closed

I read this post at “dive into mark” last night, and whilst it’s MT specific, the general point is valid across a lot, if not all, web applications.

Then I read, at Fembat that Six Apart has responded. Good for them I say. Until I read this:

“The single CPU usage statement was not intended to be in the license. It has been struck from the license, and everyone who has downloaded Movable Type 3.0 thus far can officially consider this change retroactive.”

I’m sorry? If it wasn’t intended to be there, then WHY WAS IT? Not the type of thing you miss really is it…

So again I ask, was this announcement rushed out as a reaction to Blogger’s revamp (and underlying refocussing of their product), or is this just a hugely unprofessional and basic mistake by Six Apart?

I’m not going to comment on this further, as I said before, I’ve tried an installation once, but don’t use Moveable Type anywhere so it’s a little unfair of me to chime in.

BUT – there are implications here, as Mark points out in his post, for EVERY web application. I WILL be commenting on that.

But not too much as I’ve been told that this place has been to serious recently… or something like that… to which I say WIBBLE!

Comments closed