[TYPO3-dev] The extbase dilemma

[Zachary Davis]

I think this conversation is fantastic. It's great to get the 
ExtBase/Fluid problems out in the open, as long as doing so leads to 
them getting fixed. Many people in this thread have tied their 
livelihoods, in one way or another, to TYPO3, and we're all on the same 
side. We can't go back and time and change what's been done, which 
leaves us with just a few choices:

1. Isolate and fix the major performance issues in ExtBase and Fluid, 
even if it means pragmatically straying, at times, from some of the 
principles of FLOW3 and DDD.

2. Don't fix these issues and declare ExtBase alpha or beta and think of 
it primarily a FLOW3/DDD teaching tool rather than as an "enterprise" 
framework. The side-effect of this choice is that we're left with piBase 
as a framework for building extensions. Does anyone really want that?

3. Wait another X number of years while somebody replaces ExtBase and 
piBase with something else.

I think it's clear that the first option is the only viable option for 
the TYPO3 project, and we should focus on ways to make that happen. I'm 
sure I'm not alone when I say that I have a vested interest in seeing 
ExtBase/Fluid become a viable foundation for TYPO3 extension development 
at _ALL_ levels, and I'll back up that interest with developer hours 
from guys on my team. I'm sure others on this thread will do the same. 
What we need, for this to happen, is project leadership that is 
committed to aggressively delegating tasks to people who are willing to 
publicly commit to improving the framework. I can't speak for others, 
but my developers and I are willing to help, but we need clearer 
guidance than "pick a bug in the issue tracker and fix it." Instead, 
assign us an issue that needs to be solved--even a big one—-give us a 
general description of how the project leader(s) thinks it should be 
resolved, and we'll try to code a solution. I'm sure there are a lot of 
other agencies with talented developers on board who would respond well 
to the opportunity to contribute to and improve ExtBase with the proper 
guidance.

Indeed, I often feel that the biggest problem with TYPO3 is the lack of 
a strong leader with the authority to prioritize development and assign 
tasks, someone to really drive the TYPO3 V4 project--still the most 
important part of the TYPO3 project in terms of client interest and 
revenue for any TYPO3 company—-forward in a unified direction. Perhaps 
I'm naive though, and the only way to get things done is to wait for 
individuals to get around to doing them.

Zach



Chris Zepernick {SwiftLizard} wrote:
>
>> This is a good point and it makes me think that we need an architect in
>> TYPO3, who will take care of building the architecture and watch
>> developers to stay on the right track.
>
> Hell Yes +1, to my mind that would help alot. But it has to be someone
> the people listen to.
>