[TYPO3-dev] The extbase dilemma

[Daniel Hinderink]

Hi Joey, list!

JoH asenau schrieb:

>> But actually the problem we have to face is, that people are told:
>> "TYPO3 is an enterprise CMS which is NOT aiming for the average user but
>> for larger projects only" - (at least this is what I have been told by
>> different T3A official at the last events I have attended)

Don't know about them officials exactly, but I could make an elaborated 
guess :-)

And of course it's always a bad idea to raise expectations beyond what 
can actually be delivered. (Let's pretend for a moment, that this wasn't 
what sales people do for a living). I would still say TYPO3 is a good 
choice for serious web communication needs, even if the word 
"Enterprise" is certainly history.

Let's also pretend there actually is still a CMS-market out there, 
rather than an even more fragmented landscape for specialized solutions 
that ate up content management and now mention that only somewhere below 
the fold on their feature list.

Still all that criticism about how TYPO3 is marketed, should not make it 
impossible to ask, if the software is as good as it could/should be.

The question if ExtBase could have been better, thereby avoiding some of 
its current shortcomings with reasonable additional effort must be 
valid. Of course you can put in "DAM, "Workspaces", "TempelBöller" etc. 
for ExtBase, I think.

Perhaps the will to accept that may be those Doctrine folks have got 
something going, that you can't match in any reasonable amount of time 
was missing.

May be the will to follow major changes in FLOW3, with a rewrite of 
ExtBase in substantial parts wasn't strong enough.

In any case the claim to introduce principles of v5.0 in 4.x has been 
kept and even now it's being defended here.

I think to keep that claim, ExtBase should have followed FLOW3 more 
closely, it's not enough to reduce that claim to "but hey, we've still 
got DDD over here!"

Also here at my campfire, we have been crying about performance issues 
of ExtBase too just yesterday. It couldn't solve a reasonably simple 
task in any reasonable time. Not a biggie, nothing serious is happening 
to the project. Frankly, we wouldn't have built anything serious based 
on ExtBase or Pi anymore.

So, for the umpteenth time TYPO3 has got an unfinished software 
construction site, but gladly also Basti facing the daunting task to 
turn that into something everybody wants to use.

What can be harnessed from this wave of criticism (as Jochen already 
pointed out before me) are more concise descriptions of problems, 
complete with performance data.

I'll see to that being produced from our side, but I sincerely hope all 
of you that have similar experience make this minimum effort as well, 
just as Dan Brün has been offering.

best

d