[TYPO3-dev] TYPO3 heresy: what about "selling" pro extensions?

[Jigal van Hemert]

Steffen Müller wrote:
> On 23.04.2010 12:00 Dmitry Dulepov wrote:
>> I have reasons "against" FLOW3. Do you have reasons "for"?
> If you comapre FLOW3 with existing TYPO3 code: The new code is much more 
> easier to read and understand than v4. (think of TCEmain)
> Using pattern also helps to understand ideas behind code without the 
> need to read it completely. Of course using pattern for the sake of 
> using pattern is not good. But used if they make sense, they help 
> learning a system faster.

That might be a reason for a FLOW3 developer, but when I'm working on an 
extension for TYPO3 I don't want to read the code; I simply want to use 
it. And the rule "my code is my documentation" should not apply to 
today's projects.

For me TYPO3 is a nice framework for building websites for a large 
number of reasons:
- it handles often needed features such as login, editing content, RTE, etc.
- my extensions can use a lot of features supplied by the core 
(TypoScript configuration, flexforms, BE forms, image handling, 
templating system)
- it is reasonably easy to modify behaviour of existing code with hooks 
and XCLASSes

The big questions are of course: what is so great about FLOW3 that 
none-core developers will want to use it? and: what is so great about 
FLOW3 that clients will want the developers to use it.
- it's new; that's no pro, it's more a con (new often means buggy)
- it's cool; :-x
- it uses DDD; how does that help?
- it's slow
- ... ( please fill in the advantages ) ...

-- 
Jigal van Hemert
skype:jigal.van.hemert
msn: jigal at xs4all.nl
http://twitter.com/jigalvh