[TYPO3-ect] ajax and class per controller model

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Fri Jun 29 13:45:01 CEST 2007


> 
> sure - the usage depends on what to do. the eID-Method is good for some
> easy things, it's faster because you can decide in the php which part of
> TYPO3-Corefunction you need.
> So it's only an alternative, but also positive is that it's build in core.

Hi, 

I think the prototype example shows a central problem of TYPO3 development
very well. 

The use of prototype is justified in special, well reflected cases, but
unreflected usage as default will always be harmfull. 

Still to many developers think that something is "positive" or "best
practice" only because it's in the core or because Kasper has presented it
in a video or because it's generated that way by the kickstarter. But IMHO
that's to simple. A big part of the rubbish in TER is a result of this
uncritical thinking.

A lot of things that people take as orientation is not that way because it's
good. It's only that way because nobody likes to do the work to improve it.
So it's good to keep this in mind.

Regards

Elmar

















More information about the TYPO3-team-extension-coordination mailing list