I don't know which message you have received, I didn't send you any message. I like LINQ (to object) and I care about what people say about NH; perhaps I listen some different people than you.
On Tue, Nov 23, 2010 at 12:12 PM, Wenig, Stefan <[email protected]>wrote: > Fabio, > > > > this is really frustrating. Now that the LINQ provider is almost ready for > showtime, all we’re hearing from you is basically that you don’t care > because there’s 50 other ways to query NH, world of choice, etc. > > > > As far as LINQ support goes, this is not a 1.0 release, this is a beta. A > 1.0 release could live with a limited scope, such as no outer joins or > grouping, but not with completely arbitrary failure to execute many > non-trivial queries. And I don’t believe there’s a lot missing to get to a > stable, well-defined 1.0 release. A few bugs will always be there, but > that’s not the same thing. > > > > I’m not saying you need to stop NH3 in its tracks until LINQ is fully > supported. I only said that **I** would **consider** delaying it a bit if > there’s a chance to get **some** stuff done right now. Patrick seems to be > on it, so why don’t you show him some love? > > > > If you’re not delaying, there should be an early public announcement of a > 3.1 release, and LINQ support should officially be declared beta for LINQ in > 3.0. I’m repeating this because you chose to ignore it. > > > > Now you don’t like LINQ, and you don’t care what people think about NH. > Message received. But I predict you will be the first to wipe the floor with > anyone who dares to call NH3 a piece of crap because of LINQ problems. Why > not address the problem before that happens? > > > > Stefan > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Fabio Maulo > *Sent:* Tuesday, November 23, 2010 1:35 PM > > *To:* [email protected] > *Subject:* Re: [nhibernate-development] Re: NHibernate 3 and Linq Provider > > > > From my point of view Linq is just another way to query the DB using NH. > > Linq is not more strongly typed than QueryOver and is not more easy to > learn than HQL. > > > > "Strategically" Linq is important... a strategy for what ? a commercial > plan ? a war ? a competition ? > > > > We are at one year of NH2.1.2 who has +104000 downloads, the Linq provider > for NH2.1.2 has 25000 downloads; 25% of NH's are really interested in Linq ? > > > > Yes, the actual implementation of Linq is limited; one of the session of > the nh-day Europe was dedicated to these limitations. > > We can show our limitations even in a day fully dedicated to NHibernate. > > > > For years I saw demos where the capability to translate a Linq sentence was > the center of the "show"... until a DBA have seen the ugly and inefficient > queries generated. > > > > Do you really want wait until we have a full-supported-Linq, before release > NH3.0.0 ? > > > > I prefer to give some others options about the configuration, another very > powerful and strongly-typed query system (QueryOver), new dialects, > new natively supported types, various bug fixes and some improvements to the > 75% of users working in "the dark side of the force". > > > -- > Fabio Maulo > -- Fabio Maulo
