I have received a curious opinion about ConfORM through Twitter. For some reason the twitt was probably deleted but I have the image:
Nice to meet you Jeremy!!
This is part of my first post about ConfORM:
The API proposed in the previous post is pretty good but the underlining implementation is too much strongly typed to be reused in a non-strongly-typed task.
I was thinking in begin a new proof-of-concept but two weeks ago somebody have asked me to write ~400 mappings of a domain created from various XSD… perhaps to join business requirement and Open-Source pleasure is not so hard.
The motivation around is pretty clear and I hope that your mind is enough open to understand “the underlining implementation is too much strongly typed to be reused in a non-strongly-typed task” and which is the non-strongly-typed task.
In the NHibernate’s development list you can read this mail:
I'm going to begin the implementation of "Loquacious mapping" in the trunk.
- API proposed in my blog (generics and strongly typed)
- *Mapper implementation as studied in ConfORM (namespaces ConfOrm.NH
and ConfOrm.Mappers ), neither generic nor strongly typed.
Again in the NHibernate’s development list you can read this mail:
> What benefit is this if FluentNH already does something similar?
Before somebody else continue with the same question I would like to have an
answer to these questions:
Which is the benefit/differences between:
Win7, MacOsX, Umbutu... ?
NUnit, MbUnit, xUnit ?
Spring.Net, Castle.Windsor, LinFu, AutoFact, Unity, StructureMap, Funq ?
MsSQL, Oracle, MySql, PostGres, FireBird, SqLite.... ?
Log4Net, NLog, EL-Logging ?
LinFu-AOP, Castle-AOP, Spring-AOP, PostSharp, Cecil ?
J#, C#, VB.NET, Delphi.NET, IronRuby, IronPython ?
When somebody will explain me, in detail, why we should have so many options
to do the same I will explain why I want start a different project.
Part of ConfORM is a study of some classes you will see in NHibernate3.0 and are oriented to those people want write something to map NHibernate (including Fluent-NHibernate).
We (NHibernate team) heard the phrase “Instead of making the necessary structural improvements” and the answer is the same Ayende gave more than one year ago: “a patch is welcome”. We was waiting a patch or a proposal and we are still waiting.
I never said why use or not use Fluent-NHibernate because for me is an option to map a domain for NHibernate, as others options. To have many options to achieve the same goal is the heart, or may be the consequence, of the evolution.
Take it easy and be happy!!