tag:blogger.com,1999:blog-2813261110497121234.post6305634278947771311..comments2008-01-26T12:33:00.116-08:00Shane Harviehttp://www.blogger.com/profile/01016971334424471677noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2813261110497121234.post-13487853989079804522008-01-26T12:33:00.000-08:002008-01-26T12:33:00.000-08:00I don't know that these issues are being abandoned by the standard outlets; I think, rather, that they're hidden inside non-obvious sessions. For instance, the whole Presenter thing last year could be seen as part of this discussion - and I think that the increased focus on REST (and therefore resources, which may or may not be linked to AR models) may help drive awareness, too. It's definitely good to bring up the issue, though - any chance you might be proposing talks on this to local Ruby groups and/or conferences?Benhttp://www.blogger.com/profile/09428840911994271313noreply@blogger.comtag:blogger.com,1999:blog-2813261110497121234.post-45752849132995342892008-01-25T19:14:00.000-08:002008-01-25T19:14:00.000-08:00Yeah, it's interesting. I think that because rails gives you such a great head start with laying out your code in the MVC architecture, there's a tendency to try to wedge all objects into the two types of in-built classes - controllers, model objects (those that inherit from ActiveRecord::Base), and view templates. There seems to be an opinion that to move away from the typical rails app by adding layers, or even plain old ruby objects, is crazy. No one seems to discuss these kinds of problems on blogs or at conferences, so either people don't deem it necessary, or they deem it so trivial that it's not worth talking about. I for one don't find it trivial though...Shane Harviehttp://www.blogger.com/profile/01016971334424471677noreply@blogger.comtag:blogger.com,1999:blog-2813261110497121234.post-26824177916624679902008-01-25T13:38:00.000-08:002008-01-25T13:38:00.000-08:00Interesting post. I am a huge fan of Domain Driven Design. Is it common for developers of large Rails apps to be unaware of how to model non-trivial domains? I have a perception, maybe an incorrect one, that this particular skill is largely missing from the Rails community.( not entirely of course )SlyGuyhttp://www.blogger.com/profile/02461060107416763003noreply@blogger.com