8 months later, in London, in a room full of key developers, Manila, Radio, Frontier was shown to be a toy.

In a few days time, I'll have completed a review of Manila. I wanted this to be honest, but in my rough notes, I'd only included the lack of exciting development/developers, performance/scaling issues as points against. Now, I realise that I'll need to include, ye olde memory leak and root bloat directly as these are the root cause of the above symptoms. Not good. To tell potential customers of a four year old memory leak, they're going to ask, "if that's not been fixed, where's the product going?"

Frontier's being open sourced at the end of this month. But this won't mean the memory leak will be fixed, possibly ever.

Userland's two products Manila and Radio need good publicity, like any blog product, service. At the moment, they get near zero publicity. I've often wondered why? Now I think I see, perhaps the new management actually need to keep quiet. Certainly, they don't label their products: "WARNING: memory leakage and root bloat will cause your server to be offline for several minutes everyday. As a direct result, we'll not sell many products, and will not afford to keep the product regularly updated, nor will many developers stay around, those that do will be bitter, and the support lists will thusly be dictatorially moderated and eerily quiet."

Still, Manila is still the most comprehensive and easy to use CMSs on the market. You've only to ask my football meatheads or The Government Office for the West Midlands. Neither of them notice the memory leak.