jimph wrote:
I am trying to choose a framework for our project. The question why we are not using NHibernate will certainly arise from many as it is known to many. Similarly, keeping aside the solid designer, what does LLBLGen framework has that cannot be achieved by NHibernate (for me LLBLGen various options for customize/optimize access layer is superior, for large scale development).
to name a few things:
- The Linq provider of nhibernate is still not able to do left joins and is less mature than ours.
- It's unlikely NHibernate will get an async api (ours is in beta for v4.0, see customer area)
- NHibernate is very slow. See: http://pastebin.com/AdsKitr3
It has its uses and has stuff our framework doesn't (real value types, poco classes), but in practice, does one really need those?
Bugfixes are not coming very quickly in nhibernate as well, progress is rather slow. We fix bugs within a few days, tops.
But no worries, you can switch frameworks inside the designer at any time.