Hi, Gunnar! Yes, I feel exactly the same! Just as an example, there are lots of structures for representing an entity or a property's metadata. Not entirely related, but maybe this "overengineering" is responsible for some slowness, that is often reported (mostly by non-NHibernate users, it's true). However, I think that a major refactoring is not likely to happen, precisely because of Hibernate. We are constantly looking to the Java version for fixes to bugs that show up. My 5 cents! :-)
RP On Tuesday, October 21, 2014 10:37:13 PM UTC+1, Gunnar Liljas wrote: > > When researching bug fixes and enhancements, I'm often struck by the > enormous complexity of the NHibernate code base. It's a complex and very > malleable product, so a high degree of complexity should be expected, but > sometimes when following a query from start to end in the step debugger I > just want to scream "are you frelling kidding me?!". > > Of course there's a certain amount of "this shouldn't be so hard" > followed by "Ah, OK, I didn't think of that. It is hard.", but some/many > parts of the code base feels like it has been mended a few times too many. > > My question to you, fellow developers, is: > > 1. How do you feel about this? > 2. If massive refactoring is a way forward it would likely result in a > deviation from the Java Hibernate relationship. How do you feel about that? > > > Best regards > Gunnar > > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
