Tuna - to be perfectly honest, that was a bullshit response on your part. I really do not think ANYONE thinks the performance of NHibernate.Linq is on par with L2S. Not only that but using Nh.Linq is painful at best when it cannot do quite a few things that L2S or L2O can do. Doing almost anything in the where clause pretty much guarantees an error from NHibernate.
I am really glad the framework is going in the direction it is, but when I see people such as yourself just toss a users observation aside because he did not include empirical evidence, I call bullshit! Cheers, Alec Whittington On Mon, Oct 19, 2009 at 3:32 PM, Tuna Toksoz <[email protected]> wrote: > http://lkml.org/lkml/2000/8/25/132 > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > > On Tue, Oct 20, 2009 at 1:30 AM, aemami <[email protected]> wrote: > >> >> Comparing NHibernate's LINQ provider to the only other ORM I have >> tried, which is LightSpeed, the performance of queries for NHIbernate >> is horrible. It is at least 2 to 5 times slower for fairly basic >> queries. >> >> You guys really should focus on LINQ. Most people don't want to use >> the Criteria api or HQL. That is NHibernate-specific technology, >> which is silly to learn when you could be learning a mutli-use .NET >> technology such as LINQ. >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
