I jumped on the Ruby/Typo bandwagon a few years ago since I needed a trivial, personal, blog that used SQLite and was interested in Ruby. I was coming from WebAPP. Well, as you know, Typo uses Ruby on Rails and all the requirements that entails. It is not light weight in server resources, requiring over 512MB of RAM just to update Ruby Gems. In fact, I’ve had `gem update` lockup with 512MB and had to upped the RAM to 768MB just to get it to complete. That isn’t a problem for a home-hosted server running in a VM, but at a hosting provider, that change almost doubles the monthly cost. I also ended up running pound as a front end to Mongrel running 3 instances since requests were taking too much time.

I’ve noticed that Typo RSS feeds broke sometime around 1/1/10. I also missed some of the other features that disappeared rather than being disabled by default. I can appreciate that some users had problems with them, but I didn’t so why remove them completely?

After seeing the results of your migration, I’m convinced and will be migrating within the next month. My dislike of PHP is great. I’ll be going with MT in my first migration attempt and may drop back to WP if that fails. I know perl.

If these are too complex, I’ll just go with Joomla or Drupal which will be helpful in my day job.

For the most part, I’ll miss Typo. There are many excellent things about it. I just wish it had better regression testing built into the release process.

For anyone seeking Typo help, the IRC support room is fantastic. Every time I’ve asked a question, it was answered accurately and quickly.