frameworks

This is a cautionary tale, a what not to do when faced with a bug comes and goes and seems intractable.

We are working on a customer project with an O/RM persistence layer. We're using NHibernate, and up until recently, it's been a joy to work with. I say recently, because about a week ago, our project started to load from and save to the database in an increasingly slow fashion.

I'm really loving that the Castle Project wrote an ActiveRecord implementation. But one thing that I really miss from the Rails implementation is all the runtime dynamic missing_method goodness that comes from Ruby itself.

For example, consider the standard blog example, with Author.cs, Blog.cs, Post.cs and Comment.cs. All of these inherit from ActiveRecordBase (or one of the validating versions). However, in each child class, you have to put code like

I've been working for a while on one of our stealth projects, a little Rails app that we might be finished, oh, this side of forever. However, it's been a tonne of fun wrapping my head around a new framework and some new ideas, so even if it doesn't come out soon, it's been worth it.

So, after I got finished bashing Eclipse and Aptana for eating my Ruby files, I got around to finally getting the upgrade done. And the new Aptana RadRails suite is pretty good.

It's what the community knows.