Without getting into the NHibernate questions directly, I believe it is critical to point out that maintaining “old ways” has severe limitations and is a major inhibitor of being able to make the best use of modern facilities. I have seen this cause severe problems over the 40+ years I have been involved in software development.
Using new approaches opens up new vistas, and makes practical things that were only theoretical discussions even a few years before. Since the question is about a new project, I suggest a forward looking approach. Which approach is most likely to be the basis for a roadmap that will be applicable over the next 3-5 years (or even longer depending on project scope)? From: [email protected] [mailto:[email protected]] On Behalf Of Fred Sent: Monday, December 24, 2012 4:38 AM To: [email protected] Subject: Re: [nhusers] Is NHibernate dead? As far as I'm concerned, I'm using NHibernate in all my projects involving a SGBD and the 1.2 (that means since 2007). Due to my job (running a company, serving my clients,etc…) I don't have much time to participate. However your question seems to me a bit useless (My english is not perfect / I don't mean to be rude) The question of storing objects into SGBD has been solved 10 years ago with Java and NHibernate (as a port) has been doing it for over 6 years. I know that every developer like the fancy stuff (lambda, fluent…) and hype coding-ways, but stability is a key when providing technology. If you look at EF, nothing you learn with V1 applies to V5, it is a constant re-invention of the framework - Yet on a very fast release sequence If you look ad NHibernate, everything I learned does still apply, and my (old) user judgement today is that you cannot invent content : what would you expect in other releases ? I would more likely trust a framework that has evolved according to its underlying technology (.net) and yet perhaps slowing down because it's mature, than choosing a framework because it is Ms stamped with 4 different rewrite in the timeline. Most of people wants to choose the framework for fallacious reason (linq, lambda), and when using ORM they will continuously ask the same questions (slow performances on huge graph, distribution / wcf)… Good luck for your project, AND MERRY CHRISTMAS TO ALL ! F. Le 23 déc. 2012 à 16:59, Elio Batista <[email protected]> a écrit : Hi, we are about to estart a new project,big one, and we have to choose between NHibernate and EF. I am a huge fan of NHibernate so i'm inclined to use it but as i see the NHibernate development has slowed down to a point that i'm concerned of his future and the impact of development in this new project. What you people think about this? Thanks -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/MIquQY4oPCsJ. 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. -- 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. -- 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.
