Am 19.02.2007 um 11:53 schrieb Chris Lear:
> If what you mean is "never write client-side code, when you can > auto-generate it using server-side code (on a server of your choice)", > then maybe you have a point. I don't like it, but perhaps it's the way > the world is going. Time will tell. I don't think it really goes into an all-out generating stuff for the sake of it way, but judging by what Rails wants to achieve, it's "taking the chores" out of development, and allowing everyday easy stuff to be encapsulized (not really hidden) by the framework; like Activerecord does for most DB queries/updates and RJS for most Ajax behavioural returns. You still get all the underlying interfaces (SQL for Activerecord, Javascript for RJS), so you can have the best of both worlds, as opposed to both having a strict layering that's favoured by some of the "enterprisey" frameworks out there, or the other "extreme" of hand-coding everything. The best frameworks are those that don't get in the way of what you want to do, but really help you out in most cases to allow you to concentrate on the more specialized things. Best, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
