[TYPO3-50-general] just to argue a bit: What about Doctrine?

[Fernando Arconada]

ok, now I have the why, may be this should be wrote in the wiki or similar

Thanks to every one

Whith every piece of software that i work i try to ask myself if that was 
piece already there and if is it better than my code. Reusing the code is 
good in many aspects but to remark one, it is good to easy the entrance 
the new developers to the project, lets the software grow faster and with 
more quality

If you couldn't reuse the code and you have to write a new library, then 
that kind of decisions should be written with their "why" this project 
not only it is a democratic piece it also has to look like a democratic 
piece (i'm not telling that TYPO3/FLOW3 doesn't look like a democratic 
project only that those kind of structural decisions should be writen)


Thanks again to every one

El Mon, 09 Nov 2009 10:40:54 +0100, Karsten Dambekalns escribió:

> Hi.
> 
> On 07.11.09 12:35, Fernando Arconada wrote:
>> I only want to know, Why the TYPO3/FLOW3 solution (of course i'm only
>> talking about ORM) it is better than Doctrine? Why dont integrate
>> Doctrine?
> 
> Simply put, when we started Doctrine 2 was not yet around the corner.
> And since it still shares most of the stuff we dislike about common ORM
> tools, we'd still develop our own solution, probably: configuration.
> 
> In FLWO3 you simply define your model and are done. No XML, no SQL, no
> anything. The actual persistence backend and data mapper are relatively
> slim (when not taking the CR into account). We feel it's better than
> using a tool that is far more flexible then we need, and eating the
> configuration overhead as well.
> 
> The current way of storing data as done in the TYPO3CR is less than
> ideal, but this is to be changed.
> 
> So, all in all we'll have a JSR-283 CR coupled with a slim "OOM tool"
> that exactly fits our needs.
> 
> Does that sound sensible?
> 
> Regards,
> Karsten