I have been hearing a lot about the death of the repository pattern. People using listen when such influential people such as ayende: http://ayende.com/Blog/archive/2009/04/17/repository-is-the-new-singleton.aspx speak.
This is a direction which i really don't understand and hence my post. Maybe i don't get the point because of my limited experience with ORMs. I have played with Linq2SQL & EF1. I pretty stopped when i found out the dependency requirements. I know EF4 has solved some of those problems. Having never worked with NHibernate i don't know what the story is like there. I understand the problems with a repository especially when you have really complex query logic but i just can't see how replacing the repository with a dependency on an ORM is a good design decision. For example look at Linq2SQL that pretty much died a quick death.
To me using an ORM behind a repository is just fine and dandy just as long as you don't plan to replace your repository with the ORM which i think could add maintenance problems in the future. I don't know maybe i fail to see the point because of my limited exposure working with ORMs?