[TYPO3-dev] FLOW3 / TYPO3 5.0

[Zachary Davis, Cast Iron Coding LLC]

I for one appreciate the work that Karsten and Robert and other 
FLOW3/T35 contributers have done to date. Hindsight is 20/20, Dmitry, 
and it's not right to blame "R&K&S" for making mistakes in the process 
of trying to find a new way forward for the TYPO3 project.

TYPO3 is a visionary product -- it does a lot of things really well, and 
Kasper filled it with a number of innovative, creative ideas. However, 
the problems with the codebase are countless and I think it's correct to 
say that the core is probably not fixable. I was around when FLOW3 
started, and I remember what the code looked like -- and still looks 
like -- in the most popular TYPO3 extensions at that time. I'm as guilty 
as anyone -- my (at the time popular extension), chc_forum, was a 
procedural nightmare that quickly became difficult to maintain and develop.

At the time, I remember thinking that rejecting what had long stood as 
accepted development practices in the TYPO3 community (extensions with 
all code encapsulated in a single, 100k pi1 script, for example) was a 
positive move in a new direction, despite the risks that always come 
with a new direction. I've watched FLOW3 closely since the third or 
fourth alpha, and it's been an inspiring project, not just for me, but 
also for everyone else on my team. We all look forward eagerly to the 
day when we can stop making excuses for TYPO3's obvious shortcomings and 
start embracing a platform that we can be proud of, one that my whole 
team of developers is eager to get started with.

best,
Zach



Dmitry Dulepov wrote:
> Hi!
> 
> Jochen Rau wrote:
>> Nice rhetorical trick.
> 
> Not at all. Jochen, you did not know how it started. You did not know how
> three great guys rejected help and experience of others. You don't know how
> they lost months trying stuff that were told to be unusable. If you were
> there, you could have seen that.
> 
> It was me, who offerd help and was rejected. It was me, who worked with the
> technology they wanted to use for 2 years, saw its buggy slow code and told
> R&K&S that it is a no–go. It was me who heard "It'l be ok" said with a
> knowledgeable smile only to find after half a year that they dropped it
> exactly because of the reasons I told them all. They could have saved all
> this time. But they had to hit the wall themselves, they did not want to
> use anybody's experience...
> 
> So no tricks. It is a many years of experience. I am in this business and
> this team for too long. Don't think I am a kid. I completed more practical
> projects than many here.
> 
>> Apple has some great products. But did you ask Steve one year ago if the
>> iPad (or iSlate) will have been shipped within 2 months? ;-)
> 
> This happened *after* Steve learned the Lisa lesson. He had to fail
> severely, almost kill Apple, be fired to return back with a fresh strategy
> and new ideas that make him king. But nobody likes to learn from that...
>