Firstly, Congrats on the release of the book. I have heard lots of RoR, but havent really met a programmer out here in India to gimme the details about it.
Few starters questions I have , Is is server side or client side?? Is it gonna take over PHP?? Why should a person choose RoR (advantage of over other scripting language)?? Mind a brief introduction about your book and its content??
I have a question about RoR. I'm a Java developper, using tools like Maven2 and using things like "convention over configuration" (even in my last development, for a dynamic class loading based on xml elements and attributes). I'd like to hear what is RoR understanding of the "convention over configuration" and how the concept is implemented. I mean how easy programming becomes if conventions are respected, and how fast complexity increases in case a configuration choice is made.
Thanks to you, and congratulations for your book Frederic
Rails tightly integrates the concept of convention over configuration. While you can deviate away from conventions it is best to follow the conventions because Rails can automatically derive information that way. If you have a model named list and you have a table in your database named lists, rails can automatically derive information from that database.
One of the big differentces beween Rails and (say) Maven is that in Rails, everything is integrated--it's all Ruby code, and it's all dynamic. Combine with with the conventions, and you dramatically reduce the overhead on a developer: you can, for the most part, concentrate on the important stuff--getting the job done--and leave it up to Rails and Ruby to do all the knitting for you.