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

Reply via email to