[TYPO3-dev] The extbase dilemma

[Daniel Brün]

Hi folks,

stormy weather today in framework-country! ;-)

First of all: The early comments regarding our decision are not that wrong.
We decided to go for extbase knowing that this a little risky. We really
have a bunch of experienced developers here that are able to fix things
themselves, that made us more confident to be able to cope with whatever
problems might arise. Still, we reached a point where our developers
proposed to switch technologies.

My fear is that many other agencies that are not as software-focused as we
are just do not know that there are problems. You really have to dig in
extbase to find this stuff out, because it is not documented anywhere!
Everyone gets the impression that extbase is a finished product and the
future of TYPO3. A search on web or twitter for fluid or extbase almost
exclusively results in people cheering this framework up.

Of course, we will gladly supply examples and benchmarks for the problems we
found.

What is lacking in extbase is some kind of CTO that monitors the development
of the framework, a decent code review process and thorough quality
assurance. With structures like these in place we would probably feel much
better today.

Cheers,
Dan

2011/5/18 Maximilian Kalus <typo3 at beimax.de>

> Dmitry Dulepov:
> > > Extbase is not too powerful at all.
> >
> > But simple to create extensions.
>
> Well said and true. That's what I like about such frameworks :-)
>
> But: On the one side you have a framework, on the other side you have a
> specific project you want to implement. Trying to marry both will quite
> often mean doing things that were never "intended in the framework".
> This is not a problem specific to Extbase, you will encounter them in
> Symfony, CakePHP, CodeIgniter and all those other ORM-Frameworks out
> there, too.
>
> The blog example shows an easy use-case for Extbase - in real live you
> would want to include multiple dynamic frontend-upload fields,
> complicated acls, cached PDF-generation, data-import from a remote XML
> source using SOAP and a scheduler task depending both on the flexform
> data entered in the plugin and TS. Oh my - such things are real fun in
> Extbase ;-)
>
> Still, there are many reasons to use extbase - not only FLOW3. How often
> have I fought with applying changes to quick-and-dirty extensions after
> the original programmer had disappeared and the code was only compatible
> with TYPO3 3.8? I find Extbase really helps in such cases, forcing
> programmers to code better (generally, at least).
>
> Best regards,
> Max.
>
>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>