tag:blogger.com,1999:blog-25093835.post114383783962595804..comments2007-04-16T12:07:48.879-07:00Adam Schepishttp://www.blogger.com/profile/18159615789256514603noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-25093835.post-1145404178258874102006-04-18T16:49:00.000-07:002006-04-18T16:49:00.000-07:00The MVC model transforms a complex problem into a clearly defined one. Remember those nightmares with PHP scripts where you were calling the database, reading from it, interpreting the data, studying the cookies and POSTS and GETS and deciding the show off all at once (until you learned to put a couple of lines apart in a different file, but all and all it was still the same thing just a little enlighted)?<BR/><BR/>So here we have clear and distinct programming wires and schemas. And whether your model would not be well defined, it would immediately show up along the programming and testing processes. That is not a full merit of Rails, but it gets benefitted from the full use of that paradigm.<BR/><BR/>No more invisibility. So I bet that's 4 on 4!miguelsannoreply@blogger.com