Task #50964
closed
Extbase should not be implemented as "mandatory" part of the Core or TYPO3 Main-Features
0%
Description
I recently came to the conclusion, that Extbase should not be delivered as mandatory part of the TYPO3-Core anymore.
Currently Extbase is integrated as Sys-Extension in TYPO3-Core and also some existing Extensions, that belong to the TYPO3 main-features still base on Extbase making it mandatory (f.e. Workspaces as far as I know).
You are shurely asking why?- The current Extbase ORM (Database mapping) does not even support the following base-functions of MySQL in a working manner: COUNT, GROUP BY, FIND_IN_SET, CONCAT
- Shurely the Extbase MFC is a really good work and start - but it still not readed "stable" status! But why then it is delivered with TYPO3-Core and used in some of the Backend-Features?
- There recently has been a hot discussion (#50635) regarding some "basic" features still missing in the Extbase-ORM / Database-Mapping. Someone stated that "Extbase was always meant to be a playground for trying a Flow-style of development". That user is a supporter of Extbase, but saying itself, that it is not ready fort production yet?
We are also three developers "trying" to use Extbase development now for about nearly one year. Most users and books say that Extbase has become "the new" way of TYPO3 programming.
As MFC was very welcome for us in TYPO3 development, we've done some business-projects for our customers as Extbase was never mentioned to be "unstable" or "incomplete". There it turned out, that some really nifty and basic things simply don't work at all. Most common these errors where basing on the current ORM/Database handling Extbase is using.
We had to invest a lot of time to do hacks, tricks and even "trick out" Extbase-Repositories by using regular MySQL-Statements.
But I don't think this is a clean and stable way to develop clean code!
I'm really not want to blame Extbase or the hard time developers have worked on it! But I don't understand why there hasn't been used some existing, well-engineered and tested ORM. We also work with Doctrine in some Non-TYPO3 projects. This has all the pro's of Extbase-ORM and even more.
I write this bugtrack because Extbase should be delivered using TER for those one really want to work on it. Extbase should be set back to "unstable"-state to not confuse developers investing time into production projects, that is making them frustrated and forcing using unclean programming to trick out Extbase.
Extbase is really welcome to me as a MFC-Solution. But not until it has become really stable and covering those features that TYPO3 and MySQL already offer as basic functions.
Updated by Wouter Wolters over 11 years ago
- Status changed from New to Needs Feedback
This not a task you can decide on your own. So IMO please discuss this somewhere else and not in a bugtracker!
Furthermore if you drop Extbase most backend modules won't work anymorem they depend on extbase and fluid and there is for sure no one that will rewrite these extension again!!
You are not forced to use extbase. PI-based development still works like it did before.
Updated by Gabriel Kaufmann / Typoworx NewMedia over 11 years ago
Where else should I discuss this when not here?
Imho Extbase currently has a lot of bugs and doesn't make TYPO3 more stable and reliable than without.
So tell me where to discuss it.
Updated by Wouter Wolters over 11 years ago
Try the mailinglist/forum.
For me Extbase works fine in my usecases. If you find a bug you can report them and provide patches for them, so the bugs will get fixed instead of this endless discussion which IMO will lead to nothing.
Extbase is already in since 4.3 if I remember correctly. So just dropping things is a no-go!!
Updated by Philipp Gampe over 11 years ago
- Status changed from Needs Feedback to Rejected
Extbase works fine for the current backend modules used in the core.
Just because it does not work for you and does not support all features you need, does not mean that it is useless.
On top of that, the code created for extbase backend modules has very few dependencies on extbase itself and is far more stable and reliable than the old code it replaced.
Because some backend modules (like the extension manager) depend on extbase, we can and will not drop it. The inclusion of extbase in the required modules list is backed by the core team (including active contributors) and will not be changed.
If you want to discuss something, then please go to the mailing list/newsgroup/forum. Just (verbally) stamping with your food will not change anything. Your questions and comments have been answered at the other issue, please do not waste our time by coming up with the same argumentation multiple times. That will not make extbase for feature complete or stable.
Closing this as rejected.
Updated by Gabriel Kaufmann / Typoworx NewMedia over 11 years ago
Well ok... but let me say telling me dropping some very basic Database-features like "COUNT, GROUP BY, FIND_IN_SET, CONCAT" is just "arrogant".
Sorry for that. And may be my questions have been answered in the other issue - but it was not a solution nor any real work-around.
Issues have been left as they are and nobody cares about that fact.