Comments on: Do more Rails! http://www.lixo.org/archives/2005/03/23/do-more-rails/ letting the problem solve itself Sat, 30 Jul 2011 00:26:18 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Douglas http://www.lixo.org/archives/2005/03/23/do-more-rails/comment-page-1/#comment-66 Douglas Mon, 02 May 2005 15:14:41 +0000 http://www.lixo.org/archives/2005/03/23/do-more-rails/#comment-66 Hi CV,

Any news about Rails development? You and Obie havenīt blogged about it anymore…

]]> By: Carlos Villela http://www.lixo.org/archives/2005/03/23/do-more-rails/comment-page-1/#comment-51 Carlos Villela Fri, 25 Mar 2005 12:45:08 +0000 http://www.lixo.org/archives/2005/03/23/do-more-rails/#comment-51 I'm not quite sure what you mean by architectural issues, given that there's only a few ways you can really go about architecting a Ruby On Rails app - you've got ERB views, ActionPack controllers, possibly ActiveRecord models and object-relational mapping. Add Action Mailer, ActionWeb Services or whatever else comes with it into the mix as needed, and you're done - no need to spend time messing around mixing and matching all frameworks (like you usually do when doing Java stuff - <a href="http://www.jroller.com/page/obie/20050324" rel="nofollow">see Obie's post about it</a>). Testing isn't much of a problem, really - Rails even generates stubs for both the functional and unit tests. It's a bit weird, though, that the unit tests depend on the database, but I still need to look into that (so I can be horribly wrong here) :) I’m not quite sure what you mean by architectural issues, given that there’s only a few ways you can really go about architecting a Ruby On Rails app – you’ve got ERB views, ActionPack controllers, possibly ActiveRecord models and object-relational mapping. Add Action Mailer, ActionWeb Services or whatever else comes with it into the mix as needed, and you’re done – no need to spend time messing around mixing and matching all frameworks (like you usually do when doing Java stuff – see Obie’s post about it).

Testing isn’t much of a problem, really – Rails even generates stubs for both the functional and unit tests. It’s a bit weird, though, that the unit tests depend on the database, but I still need to look into that (so I can be horribly wrong here) :)

]]> By: john brookes http://www.lixo.org/archives/2005/03/23/do-more-rails/comment-page-1/#comment-50 john brookes Fri, 25 Mar 2005 08:44:46 +0000 http://www.lixo.org/archives/2005/03/23/do-more-rails/#comment-50 Hey Carlos, I want to know if you think Ruby can handle all the architecture issues that a lightweight container like Spring takes care of? With Spring, the IOC configuration-based architecture supplies benefits of clarity, confoguration, and testing. You can have Spring mvc, ibatis db OR, Velocity/JSP, POJO biz objects all running in one framework and not dependent on it. Can Ruby somehow leapfrog these concerns, power through them with code? John B Hey Carlos,
I want to know if you think Ruby can handle all the architecture issues that a lightweight container like Spring takes care of? With Spring, the IOC configuration-based architecture supplies benefits of clarity, confoguration, and testing. You can have Spring mvc, ibatis db OR, Velocity/JSP, POJO biz objects all running in one framework and not dependent on it.
Can Ruby somehow leapfrog these concerns, power through them with code?
John B

]]>