This is truly a nice thread. With lots of assumptions and veiled accusations of hardened viewpoints... The other must change for my benefit (that is what I perceive)...
But let us bring in some perspective: - SAP r/3 <http://en.wikipedia.org/wiki/SAP_ERP> was launched in 2002 and was/is an evolution of something else. - JD Edwards <http://en.wikipedia.org/wiki/JD_Edwards> came from the mainframe (way back when) - The variants offered by Microsoft came from all over the world and started also way back when... And are these competitors all at the end of their individual lifecycles? I dare to say No. And do these all have (had) their share of legacy issues? And if started anew would the owners/architects/business consultants/system developers/programmers et al. behind these product shed paradigms and introduce new ones? And if done so, would these new paradigms not also require a lot of effort (of a lot of people) to implement, reach maturity and when new architects get on board lose their momentum? I dare to say Yes. What I am trying to get accross is this: It took a lot of persons to get OFBiz to where it is now. This is not only the feat of David, though his contribution is substantial. And David starting over (and shedding wrong paradigms - in his vision and perception) took him 4 year to get Moqui to where it is now. But it doesn't deliver today what OFBiz delivers. Yes, it is a clean slate. With new learning (steep) learning curves and such... But yes, when anyone needs to implement something new for a customer the criteria on which you need to choose the framework to work with is your skill set, as time-to-market dictates cost. David chose to not do the paradigm shifts within this community. And why? Anyway, that ship has sailed and that can be regarded as sad. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com
