[TYPO3-dev] The extbase dilemma

[Patrick Lobacher]

Daniel Brün schrieb:
> Hi folks,
> 
> 
> Regards,
> Dan

Hi Everybody, Hi Daniel,

I do not want to answer your posting in detail but in general...

1.) We use Extbase for every new extension since about 18 months - 
independent of the kind, size, amount of data, and so on. We have done 
small extensions and "huge" ones (uhh - scarry - we have not 
reimplemented ebay or facebook but real existing "big" data amount 
projects. We have Extbase extensions on sites with just a few visitors 
per hour and with a few 1000 per hour - and, what should I say: Nothing 
to complain about. Sure it is slower than before but there a 
possiblilities to optimize it.

2.) Of course we discovered a few problems here and there and we solved 
them as always - in the former days we had the same with the "old" and 
"stable" API - so no difference at all. There is a bugtracker - so 
sometimes we patch an urgent problem by ourself or use a patch there - 
no difference to the old days...

3.) "Alpha", "Beta", ... are just names - without any meaning (sadly) 
within TYPO3 - so tt_news is beta since 217 Years - does anybody 
complaining about it? No... And I can name you a bunch of extensions 
with the label "stable" and a lot of bugs in it - hey - it's software - 
bugs are part of them - always. The question is - are there so many bugs 
that you can't work with it? And - for me - this is not the case with 
Extbase.

4.) Extbase is not another way to programm extensions. Extbase is not 
the "new" way to programm extensions. Extbase is a new way of thinking 
about (complex) software design. Step back, forget (for a minute) TYPO3, 
Databases, Infrastructure, Forms, even Code at all. And now have a look 
at your problem, at your domain and start "doing" Domain Driven Design. 
This part (and this is time consuming and complex as well) could take 
about 10-30% of your project (if done right) and now come back to code.
You don't WANT to think about databases and UIDs and Joins and whatever.
And if you want, you have not understand DDD at all ;-) Yes, you will 
pay a high price for being withing the DDD universum (and this is 
Extbase for the moment and FLOW3 in the near future) but you get back an 
enormous reward - something you are not even able to do with the art of 
porgramming with pi_base. This is a new level which is unreachable with 
pi_base. But you have to change thinking...

5.) I've have taken a mid_size Extbase extension we have done and ported 
it to FLOW3 - and what should I say... yes it took me about half an hour 
to get this running. I've done a few changes in the classes to have the 
correct namespace and class namings (what can be done through a programm 
  for sure) - and it worked finally. So what... But - and this is 
perhaps the most important part - I haven't used any parts in there 
which are part of the old world - no lousy double triple inner outer 
something join (which just works on MySQL 4.1.21 alpha7Pre5 on Windows), 
no t3lib_something, no non @api commands, just pure DDD extbase code... 
smooth

6.) It's absolutely rare that a develeopment team does such a great job 
on the documentation of breaking changes as this happens with Extbase 
1.3. So there were a lot of documents containing all (and it was just a 
few) changes. But - as a reward of the breaking changes - we got Wigdets 
- and they are so great that (is my opinion) it was worth.

7.) Let's use the T3DD11 to discuss all matters belonging Extbase & 
Fluid - there is the point where all developer are on one place.

8.) There is a lot to improve with extbase and fluid - without doubt - 
but the team does such an great job here that everyone should really 
greatful. Extbase & Fluid (and FLOW3 as well) are one of the greatest 
usable technologies I've seen for a long time...

Just my2cents
Patrick