I’ve been working on a Ruby On Rails app for a while now (see previous post, and also Obie’s take on it), and seriously, more often than not it’s hard to stop coding; more than once I’ve looked at the taskbar and gasped in disbelief – over the past month, I’ve coded way past 2 AM after having worked the whole day, and even though I needed to wake up early the next morning, I was not tired at all. So, to put it in another words, careful – this thing is addictive.
And it’s gaining an astounding lot of momentum too, as Wilkes Joiner points out. It’s definitely a good time to have a look at it, now that the 0.11.0 version has been released. It’s still early days, and the sheer amount of functionality that’s in Rails already is somewhat disturbing. By the time this thing hits 1.0, taking over the world or entirely destroying it with it will be a matter of calling a couple of methods and putting some nice CSS on top of it.
john brookes | 25-Mar-05 at 8:44 am | Permalink
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
Carlos Villela | 25-Mar-05 at 12:45 pm | Permalink
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)
Douglas | 02-May-05 at 3:14 pm | Permalink
Hi CV,
Any news about Rails development? You and Obie havenīt blogged about it anymore…