psandler wrote:
Otis wrote:
I'll answer your email in the next 30 minutes.
Frans,
I would love to hear your thoughts on this if you'd care to share them publicly.
I burned my hands once by talking in public about nhibernate and it ended up in a nice flamefest on their forum (I posted my thoughts on the asp.net forums). So I won't burn them again.
It's not nhibernate in particular, I don't think it's that it's wise to give my vision on tools I don't work with every day in public.
nhibernate and llblgen pro follow two different philosophies: relational model drives classes (LLBLGen Pro) vs. classes drive relational model. That's a major difference. I talked about that here:
http://weblogs.asp.net/fbouma/archive/2004/10/09/240225.aspx
nhibernate and some others use POCO's (plain old clr objects), llblgen pro uses pre-baked classes. Also a major difference, and either side has it's pro's and cons.
I've come to the conclusion that it doesn't really matter what you pick, both sides will get the job done, it's though how you want to work. I still have a strong feeling that on the .NET side, people less 'domain model oriented' than on Java. Which is why I don't follow the pure domain model.
