Basically from reading the book, Dan doesn't believe in the "Rails
Way" because he hints that it lends itself to quick and dirty code;
not dirty in the sense of old PHP/ASP code, but dirty in that it
doesn't care about scalability from the start but as an afterthought.
Although his book does seem more geared towards using Rails in an
enterprise environment, as opposed to the usual new startup. He does
mention that, as a developer of an original "big Rails site" he's
speaking from hindsight in his own projects and that he would
architect them properly to scale from the start.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
