I’ve been singing the Rails front end/Java back end tune for quite a while now, especially after observing the changes in store for Java in the next year combined with the maturation of JRuby. So, when I saw this post come across the Rails list last week, it really caught my eye. Charles Nutter hits the nail on the head:
I have also been disappointed with most of the Java-based web frameworks, almost entirely due to their over-heavy, over-complicated approaches to implementing the view and controller portions of an app. If I were to write an application now, I would give strong consideration to something more Railsy, even if it were backed by Java-based services.
As much as I do like Java (really, I still do!) using it to write web apps is jut plain painful. That said, companies will be loathe to dump the massive investments they’ve made in Java over the last decade and rightfully so - but that doesn’t mean we can’t get the best of both worlds. Imagine the speed of development inherent in the Rails world combined with the mature infrastructure of Java. Sure seems to me like we’ll be doing lots of this over the next few years…
BTW, Obie Fernandez posted about this today (though I’ve been happily reading along with the earlier posts) but did you happen to notice that Uncle Bob has been getting into Ruby and Rails lately?
