[TYPO3-dev] The extbase dilemma

Franz Koch typo3.RemoveForMessage at elements-net.de
Thu May 19 15:18:34 CEST 2011


Hey,

> Well, we came up with this on T3DD09 when we pointed out design flaws
> and performance issues.
> Unfourtunately, the only way to get heard is to supply patches.
> Strategic help is not wanted (don't ask me why).
>
>> Why doesn't anyone having that knowledge and getting big rewards
>> for those enterprise solutions join the team then?
>
> See above.

that was probably back in 2009 - but I think things changed a lot since 
then.

> Well, like Dmitry states in his other posts... you'd need to do
> drastical changes to the architecture.
> Something which is kind of tricky with something labeled "stable".

That it can't be "stable" should be clear by the fact that it's a 
backport of a framework in alpha stadium, but yeah I know - it's marked 
as that, can't change it.

So the conclusion I read in your posts is to stop being a backport of 
FLOW3, keep the good ideas/concepts, drop the rest and start building 
yet another new framework attempt but this time with enterprise 
requirements in focus regardless of code quality when it comes to design 
flaws?

-- 
kind regards,
Franz Koch




More information about the TYPO3-dev mailing list