Your is the right spirit: you have to use the tool that better fit yours needs.
-- Fabio Maulo El 14/12/2010, a las 12:00, David Pfeffer <[email protected]> escribió: I definitely agree with this. In fact, I am only using NHibernate for LINQ because I am forced to, because of spatial support. If EF supports Spatial before NH has stable Linq, I'll definitely have to look there. On Tue, Dec 14, 2010 at 9:59 AM, Hoang Tang <[email protected]> wrote: > My current experience with Nhibernate is that bug get fix pretty quickly > once you report it whether it include the Linq provider or not. > > With that said I think it's a chicken and egg problem. I agree with Kakone, > most people who need/want a solid LINQ provider probably already look else > where. Without the mass user adoption, bug won't get discovered/reported, > hence slower improvement cycle. > > The good thing is that it's slowly getting better, I see noticeable > improvement at every cycle... but until we reach a certain threshold of > adoption the LINQ provider won't be ready for production until another year > or two... > > Of course that's just speculation on my part and I hope I am wrong... > > > On Tue, Dec 14, 2010 at 8:29 AM, Kakone <[email protected]> wrote: > >> "it seems to be enough stable"... It's a joke or we don't use the same >> version ? >> Yes, if you do a simple Select, it's stable. But, each time I want to >> do something a little more complicated (some simples OrderBy, Left >> Join, ...), it doesn't work well. >> Congratulations for the accomplished work but you can't say that it's >> enough stable (or we do not have the same conception of quality). >> Actually, to my mind, the LINQ provider can't be used in a real >> business application. Since Steve Strong stopped the developement, >> nothing - or almost - has changed. I'm not complaining because it's an >> open source project and all the people do their best to improve it (if >> I had time, me too), but you can't say that "it seems to be enough >> stable". All the users of the new LINQ provider think that this new >> LINQ provider is in beta state (also Patrick : >> http://blog.patearl.net/2010/12/nhibernate-30-linq.html). >> >> But, you are right, if very few new issues were added to Jira, I think >> also that the reason is something else : >> 1 - most of the users will not add an issue to Jira, >> 2 - most of the users that want a LINQ provider that works well, uses >> Entity Framework. >> And I still think you are mistaken when you think the LINQ provider is >> not so important for NHibernate users. >> >> On 14 déc, 13:48, Fabio Maulo <[email protected]> wrote: >> > at the moment 7660 downloads in 10 days. >> > very few new issues regarding the LINQ provider. >> > Perhaps I was wrong thinking that the LINQ provider will be the mayor >> source >> > of issue for the next two year... it seems to be enough stable...hmmm or >> > perhaps the reason is something else. >> > Btw, CONGRATULATION for your work! >> > >> > On Tue, Dec 7, 2010 at 12:10 AM, Fabio Maulo <[email protected]> >> wrote: >> > > Hi team. >> > > Only to be actualized about one of the result of our work: >> > >> > >http://sourceforge.net/projects/nhibernate/files/NHibernate/3.0.0.GA/. >> .. >> > >> > > -- >> > > Fabio Maulo >> > >> > -- >> > Fabio Maulo > > >
