[TYPO3-dev] Better use pibase while everyone use extbase?
Patrick Schriner
pschriner at gmx.de
Tue Oct 7 14:35:04 CEST 2014
The best benefit of Extbase development comes of the ability to
understand, reuse and extend Extbase-based extensions.
Maintaining old big pibase-Extensions (or worse: homebrewn MVC extensions)
is a nightmare. You can look at the (old) code base of direct_mail,
powermail, news, cal ... and curse a zillion times when you try to
understand there wonky behavior. That doesn't mean they didn't do the job,
but it's very hard to maintain these extensions after the original
creators have lost interest.
Extbase/Fluid is far from perfect, but from what I've seen the chances
that the code will be maintainable are *far* higher than in the old
"system".
That aside: It sucks when you need many objects. It sucks when performance
(especially uncached) is critical. I think it's downright unbelievable
that there are still issues you encounter when using Extbase+Fluid, FAL
and multiple languages. But those are solvable.
On Tue, 07 Oct 2014 11:30:50 +0200, Tim Richter <bachi18 at web.de> wrote:
> Quote: Philipp Wrann (majpay) wrote on Tue, 07 October 2014 08:51
> ----------------------------------------------------
>> Some people are simply not open for a change, even if it means less
>> work and more comfort.
> ----------------------------------------------------
> Thats still to prove.
>
> I claim, there are some cases, where Extbase might be 50% faster (in
> development), but very rarely more.
> But it other (not too rare) cases it takes 400% of the time.
> I know not a single extbase developer, who didn't swear several times
> against the framework, and required several hours to solve a problem,
> which would be 2 minutes of coding the traditional way. Usually because
> of flaws and bugs in the framework which is _very_ hard to debug, or
> even fix.
>
> On the other side, it's awfully slow. Especially when you work with data
> not stored in doctrine. E.g. when using a webservice, or solr for
> data-retrieval.
>
> The _only_ two advantages are, from my point of view, to enable rather
> stupid coders to write a semi-secure code, and to enforce code
> conventions.
>
> Basically it was absolutely over-hyped, and few very aggressive
> supporters forced it into the community. But thats usual in the
> os-community - of course there are many advantages of it. But usually -
> who trolls most aggressive, has the best chance to win.
>
--
More information about the TYPO3-dev
mailing list