First, thank you for your feedback. :-)
Alexander Schnitzler wrote:
Mathias Brodala wrote:
- property mapping, type converters (typed arrays, anything to anything)
Yes, there are bugs and flaws, accepted
Don't forget about the shortcomings due to lack of backporting. ;-)
- dependency injection (lazy)
Not gonna happen, we need a different approach for the whole core, maybe symfony DI
While I'm not opposed to more Symfony in the core we should remember the old promise that you can port your Extbase code to TYPO3 Flow without much hassle. Having a completely different DI implementation could make this harder. (Unless Flow also switches to Symfony DI)
- custom annotations
Not gonna happen due to AOP. You can implement them yourself by using the Reflection.
Been there, done that. ;-) Still nice to have.
- AOP (see EXT:autoloader)
Not gonna happen and I will fight against code generation in CMS until the bitter end.
I can see where you are coming from (AOP in Flow requires generated proxy classes) but have a look at the mentioned autoloader extension which takes care of a lot of boilerplate for frequent tasks.
- command controller (Symfony console)
Helmut Hummel works on somehting like this.
I know, I have already asked him to have my babies.
- routing
Not gonna happen because Extbase it not a Framework. Routing is a core issue.
I don't mind having this in the core either. ;-)