[TYPO3-dev] The extbase dilemma
Popy
popy.dev at gmail.com
Fri Jun 3 10:55:17 CEST 2011
Hi everybody,
Sorry for that late intervention, but I just missed that part :
> Create a new extension (Peters suggestion: nextbase).
That's sound for me as the worst idea of this long topic. That's again the
same mistake :
1. Somebody said "MVC is nice" and then the Extension Coordination Team
and lib/div appear
2. Somebody said "Flow3 is great", and Extbase came
3. Now people says that Extbase is not perfect, and you suggest to make
another extension ?
And for the third time, you want to "import" in Typo3 an external system,
which isn't adapted for the "plugin scope". Typo3 v4 is not Flow3, and if
you really want to use Flow3 things, you'll have to build a huge thing
between core and your libraries.
And worst of all, maybe it will require more Core adaptations, like it
happened for Extbase.
And will the release of that kind of extension mean the end of extbase
maintenance ? That would be crappy for those who choosed Extbase in their
projects !
Regards,
Pierre Dudoret, aka Popy
More information about the TYPO3-dev
mailing list