I don't exactly remember all the details except I dislike environments that try and mask too much complexity. When ever I start working with these type of frameworks I get find an exception that is very difficult to work around. I laugh at the demos I see that spend 10 minutes creating a classic invoice/details form in 15 minutes because it never works that way in the real world. To sum up, I get very frustrated when I have difficulty working with a framework outside of the box. Rails just seemed that way to me.
>Would you please elaborate on this -- i.e., specify a few of the things that you found particularly problematical to implement in Rails that were much more easily done in PHP?
>
>TIA,
>-m.
>
>**************
>
>>For what its worth, I tried using Ruby on Rails a couple of years ago and I finally gave up. It seems that it was written for someone who didn't want to do anything with a database. Once you had to get out of their box it got really complicated and messy. I have since switched to PHP which I like much better. You might want to look at PHP as well.
>>
>>>Hi,
>>>
>>>For a little while now I've been reading up on Ruby on Rails, a very interesting Web development framework. I am not an expert, only a curious person so far, but am going to try to bring here some information about the product and why it got me interested. Often I'll quote from a Rails site or book since it will be more correct than my attempts.
>>>
>>>Rails was extracted from an application (Basecamp) developed by David Heinemeier Hansson around 2005. It is open source, free software, now in version 3.0. The best part is not that it is free, nice as that is, but that it has very powerful approaches at the core and that it has developed a very vibrant community around it. As we know from our experience with FoxPro, the community can be a feature of a product. That is why I asked Michel to start this section for Ruby on Rails. I think people here will find it an powerful and appealing product.
>>>
>>>Rails makes certain assumptions about the type of data based applications that developers often write and provides the means to go about it very quickly, yet allowing wide ranging customization later. All Rails applications are implemented using the Model-View-Controller (MVC) architecture. All Rails applications have testing support baked right in. It has a number of powerful approaches at the core. The one I like best is "Convention over configuration". If you accept their conventions, you can save A LOT of time.
>>>
>>>Here are some references:
>>>
>>>
http://rubyonrails.org/>>>
http://rubyonrails.org/applications>>>
http://guides.rubyonrails.org/>>>
>>>I think it is really worth your time to investigate this product.
>>>
>>>Alex
