Is NHibernate dead?

[Elio Batista]

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

[Elio R. Batista Gonzalez]

Hi Mauricio, thanks for your response, as developer i agree with you
in your point.
My main concern actually come from Ohloh's analysis. I was curios
cause i noticed that projects like Castle, LinkFu,
Spring.NET are virtually idle.

2012/12/23 Mauricio Scheffer <mauricio...@gmail.com>:
> IMHO, less activity in a project does not imply its death. I have open
> source projects that I hardly touched for over a year and they work in
> production as usual, without issues. I don't touch them simply because they
> already do whatever I need them to do (and this apparently also applies to
> their users). Sure there's always ideas for cool new features and room for
> improvements (sometimes we're even tempted to rewrite the whole thing), but
> this takes time and effort. Time that can be used to (for example) deliver
> actual business value.
>
> Compare to your workplace. At least where I work, there's quite a few
> systems in production. Some of them don't get any changes in months, which
> is actually a good thing, because it means they're doing what they're
> supposed to do, which means that programmers can focus on changes that are
> strategically important or deliver immediate business value. Not everything
> has to change all the time.
>
> About NHibernate in particular, Ohloh's analysis (
> https://www.ohloh.net/p/nhibernate ) says that it has stable year-over-year
> commits, so it's objectively not true that its activity is decreasing. The
> last commit was seven days ago. Last release: two months ago. Also take a
> look at the graph of contributors per month. There's quite a bit of activity
> in this google group and in Stackoverflow. The NHibernate JIRA (
> https://nhibernate.jira.com/browse/NH ) shows many issues resolved in the
> last month and a lot of activity in the last few days.
>
> May I ask what metrics or criteria you are using that led you to think that
> NHibernate is dead?
>
> Cheers,
> Mauricio
>
> --
> 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/-/brAeHDr5NsEJ.
>
> To post to this group, send email to nhu...@googlegroups.com.
> To unsubscribe from this group, send email to
> nhusers+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.

[Oskar Berggren]

2012/12/23 Elio R. Batista Gonzalez <elio...@gmail.com>:

> Hi Mauricio, thanks for your response, as developer i agree with you
> in your point.
> My main concern actually come from Ohloh's analysis. I was curios
> cause i noticed that projects like Castle, LinkFu,
> Spring.NET are virtually idle.

But none of those projects have much to do with NHibernate. Unless
you're referring to the proxy generators, but NH nowadays has its own
as the default.

/Oskar

[Elio R. Batista Gonzalez]

Hi Mauricio, posted here
https://groups.google.com/forum/?fromgroups=#!topic/altnet-hispano/9REUVpyyRM0



2012/12/23 Mauricio Scheffer <mauricio...@gmail.com>:
> Hi Elio,
>
> You posted a question concretely about NHibernate's health in a NHibernate
> forum, so somehow your concern was about NHibernate. I'm really curious
> about what made you think that NHibernate specifically was dead.
>
> About those other projects, I can only speak about Castle (never cared much
> for the others): The ohloh statistics for Castle (
> https://www.ohloh.net/p/castleproject ) are based on *all* Castle projects,
> so they're skewed. Most of them are really dead. The ones that are still
> actively maintained are Core, DynamicProxy, Windsor, Transactions and the
> NHibernate facility. Monorail was pretty much absorbed by ASP.NET MVC.
> ActiveRecord was rendered largely obsolete by FluentNHibernate and later
> advancements in code-based configuration in NHibernate and things like
> SharpArchitecture.
> Also, many people, myself included, just don't need IoC containers any more.
> I dropped many of the libraries/frameworks I used to use because they're
> simply not worth their complexity.
> Still, if you're missing any features in LinFu or Spring, you should post to
> their respective mailing lists, get involved in their development. As I
> usually say, open source is the ultimate do-it-yourself: if you need
> something, go ahead and implement it. Never wait around for it to magically
> happen.
>
> Cheers,
> Mauricio

> https://groups.google.com/d/msg/nhusers/-/e6wTbjAf4aMJ.

[Fred]

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.

--
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.

[TheCPUWizard]

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)?