Dont misunderstand me.. thats not me talking here. This is a blog entry by Shawn Wildermuth (http://wildermuth.com/) that is self explanatory from the title. It does mention LLBL, NHibernate and Linq2SQL. I do agree with the author's take on the landscape though I feel LLBL still strikes the best balance among the competition...

Its an interesting read... enjoy

I think he's right about the point he's trying to make: don't think an (pick one, doesn't matter which one) O/R mapper is always going to be the best one for everybody.

I think O/R mapper developers should realize that too: you can't have everything: if you want poco you give up other things. Things which might not be important to you but which might be important to others. And vice versa.

That's also why our framework is the way it is: we personally think this is the way it should work, and that appeals to a (luckily ) large group of people. Though we do know that a lot of others like a different approach and I think that's cool. What I hope is that everyone who picks an O/R mapper does that because the O/R mapper chosen is the best fit for the way the developer/team wants to work. A dutch saying says "There are more roads which lead to rome than this one" (rough translation) and I think that's the point Shawn was trying to make. As long as you pick the right road for you.