[TYPO3-dev] Better use pibase while everyone use extbase?

[Jigal van Hemert]

Hi,

On 6-10-2014 15:02, Jo Hasenau wrote:
> My personal choice would be:
>
> 1. You need OO coding and want to code close to FLOW to be able to port
> your extensions to NEOS later on: Go for extbase
> 2. You need OO coding but don't care about FLOW or NEOS: Go for another
> OO-framework (but for compatibility reasons maybe use an existing
> extension if possible)
> 3. You don't need OO at all: Stick to the core API and your own code

I've often used a fourth option (also with pibase extensions):
4. Use OO coding with just PHP tools and use core API whenever possible 
and appropriate. You can simply use classes and if the core autoloader 
can't handle them automagically (naming and location conventions) simply 
add them to ext_autoload.php

The core API is great for boring stuff; database connections, login, 
templating, and so on.

Every layer that does things for you will also limit your freedom. 
TANSTAAFL If you don't like what extbase does for you, don't use it. But 
given the number of problems I see in code (security issues, cases that 
are not handled, code that works by accident, etcetera) many 
"programmers" will benefit from a framework/API that takes care of this 
for them (even if it costs something).

> And: Yes, I believe there are lots of use cases, where OO is a waste of
> time and resources. - Now start beating me ;-)

Haha. Agree with you here.

-- 
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org