tag:blogger.com,1999:blog-13540000.post494076496511181604..comments2007-10-16T21:33:50.151+05:30Gaveenhttp://www.blogger.com/profile/03708879688644127067gaveen.prabhasara@gmail.comBlogger2125tag:blogger.com,1999:blog-13540000.post-24481046485267182332007-10-16T21:33:00.000+05:302007-10-16T21:33:00.000+05:30Very true, that you cannot see whats worth till you try it. So I'm doing it. :) Sure, the OnLamp article can't give the complete picture, I just mentioned it because it shows a taste of what is convention over configuration.<BR/><BR/>As far as I know Rails is not another wrapper which simplifies common operations. Rails has design principles of it's own which help to improve the productivity. These things are factors when you have to do a complex system. Even the things like, not having to worry about configuration is a plus for me in such cases. A lot of these advantages have roots in the Ruby language. And as a framework, ..... well I'm not going (and by this point I actually am not competent enough in other frameworks) to tell how it makes things better. As you say I'd just try it more and more. More I try it more I realize that it is actually a full-stack web application framework.<BR/><BR/>I'm a SysAdmin, so I'm also no Ruby developer, but I'm becoming one rapidly than I thought. Anyway, you guys have played long enough with WS and frameworks to be far far ahead of me. :) I also hope that you'd give it a try.<BR/><BR/><BR/>PS: And.. oh, I wrote that in a hurry, even more hurry than the Git article, and I also think the Git article is better in standards.<BR/><BR/>And,... why, I almost forgot to thank you for your comments. So Thanks a lot. :)Gaveenhttp://www.blogger.com/profile/03708879688644127067noreply@blogger.comtag:blogger.com,1999:blog-13540000.post-59983882248830612542007-10-16T13:33:00.000+05:302007-10-16T13:33:00.000+05:30No doubt RR is simple and a very popular framework for doing web apps but you can't get the correct idea by just following the OnLAMP's tutorial.<BR/><BR/>It simplifies the development a lot as a result of the example (as is in many introductory tutorials) it uses but in reality developing a complex app is still going to be complex. The Q is how well the framework will assist you in such a situation as opposed to hinder you by making you jump through several hoops.<BR/><BR/>I am no Ruby developer so I cant say with certainty but I'd resever my judgement till I'd build a real world app.Budhttp://www.blogger.com/profile/16681603430019235684noreply@blogger.com