I do like Rails though. It’s beautifully elegant when it decides to work. I wouldn’t be so frustrated if my largest project didn’t have this strange and crippling bug with the model interaction.

you may also want to post about the code that have worked so far.

also, since your article hints that you still don’t know ruby’s full syntax, there’s also the possibility that your expectations of syntax leniency in one area may have conflicted with that of ruby. in elliot rusty harold’s rails walk (elharo.com/blog/software-development/2005/12/03/birds-on-rails-part-3/), he made the mistake of calling a function instead of concatenating two strings, probably because he still wasn’t too familiar with ruby’s syntax.

I’ve also tried using Turbogears for my own web apps after getting a little frustrated with Rails (primarily b/c of my unfamiliarity with Ruby). Let’s just say the database back-end is a lot more saner and comfortably takes care of your relationships. Plus, you don’t have to write SQL. I was taken aback at first by this, but Turbogears’ use of SQLobject feels so clean that I didn’t want to go back to Rails.