[TYPO3-dev] The extbase dilemma

[Daniel Brün]

Hi folks,

first of all, this goes to the extbase-team and the community in general: I
really believe in your skills, and I also highly appreciate all the energy
you put into this.

I think that a huge part of the problems we are facing now are due to
communication.

How often has the extbase-team talked to the FLOW3-developers? The
FLOW3-developers are framework-gurus by now. Have you checked that extbase
still adheres to the concepts the FLOW3-team has in mind?
If someone in the TYPO3-world knows the pitfalls you run into when
implementing an ORM, it must be Karsten. Have you talked to Karsten when
developing the persistence layer? His input is valuable!
To make it short: Have these teams as intensively communicated as would be
needed for something like this?
My impression is: not enough.

I would also imagine that a lot of communication between the extbase-team
and the v4 core developers is necessary. My impression is that the core v4
people are not really interested in the future of extbase (I might be wrong
on this one) - and vice versa.

I do not doubt that Bastian is perfect for leading the extbase team. But it
appears that after Jochens departure there is a white spot in the
persistence-department.
I was talking about some team or person that overlooks the core, FLOW3 and
extbase and makes sure that everything is aligned.

Look at the fragmentation we have now!

Again: These are my impressions and I might be wrong.

Cheers,
Dan


2011/5/19 Mathias Schreiber [wmdb] <mathias.schreiber at wmdb.de>

> Am 18.05.11 21:13, schrieb Dmitry Dulepov:
>
>  Nothing but we do not have such info for Extbase. In fact, we do not
>> have any real life use cases for Extbase. It would be good to hear
>> stories where people used Extbase to implement functionality, especially
>> on large web sites.
>>
>
> Ok, I don't get this.
> If I re-persist an object and get full table locks... what the hell?
> My data storage does not need to be large to run into problems here.
>
> @everyone except Dmitry, because he knows all this:
> I HAVE to assume at least basic profiling and math skills if someone
> develops ANYTHING.
>
> So if you build something new that takes care of stuff I have to take care
> of myself there naturally is a disadvantage somewhere.
> Sometimes it's complexity, most of the times it's performance.
>
> Compare scenario "BEFORE" with scenario "AFTER", write down the results.
> From there multiply until you think someone might run into problems.
>
> I see three possible reasons:
> a) developers are not smart enough to think about this (which I hope I can
> doubt)
> b) developers get tunnel vision and keep telling themselves "performance
> matters will be addressed later" (which should be face-slapped right away)
> c) developers don't care about performance at all (which should be
> face-slapped twice...no...four times as much)
>
> And "performance" in this case means:
> - execution time
> - scalability
> - RAM usage
> - CPU usage
>
> Really... please please please.... take these into account and don't just
> rebuild what you read in your Java books...
>
>
> --
> Ernesto, Nov. 9th 2010:
> "In the graphics generation routines of TYPO3 *anything* could cause a
> side effect."
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>