MonoRail makes life boring...
How can I take pride of solving hard problems when MonoRail takes them all away? I'm trying to build a sample bug tracking system. The problem is that I'm using MonoRail, which means that I'm in either of two states:
- The explorer state - where I just surf MonoRail code and discover all sorts of cool things it can do for me. This is the fun part.
- The implementation state - where I try to code up the site, and realize that I'm reduced to a HTML Monkey level, since all the previously admired features handle just about anything for me.
I'm reduced to writing HTML in notepad, trying to make it challanging again. Where is the complex thinking? Where is the tortured, tormented, debate about the architecture? Where is all the time spent in writing a data abstraction layer, implementing bussiness logic components, etc. Exception management and localization are built in. You need to provide 15 LoC to add security, and that about it.
I've nothing to do but decide which CSS style to use for the page. It's beyond belief. MonoRail and ActiveRecord performed a hostile takeover on my application and left me with nothing much to do beyond connect the dots. The application writes itself, and I'm dogging after it trying to make the UI look good.
To any who lacks sense of humor. I really like Castle's capabilities. It simplefy the life of the web developer by an order of magnitude or more. And I didn't even got to the point where I need to use facilities & components yet :-)
What I do see as MonoRail biggest weakness is the inability (my inability, that is) to explain the benefits to someone who only did ASP.Net programming and doesn't see how it seperating the view & the controller can help you in making the application. I tried several times this past week, and I just couldn't make them get it.
Comments
Comment preview