[TYPO3-ect] lib/div: Next to last milestone to beta release

[Daniel Brüßler]

Hello Elmar,

I see you're angry, but that doesn't help. Please don't take it 
personally and don't get it "in the wrong throat" (nicht in den falschen 
Hals) how reactions are.

== tslib_pibase, ugly architecture ==
that's the standard for the moment. That's the only stable framework 
what kickstarter creates in the moment, and it's the only one what the 
most books talk about. But times are a changing with lib/div!

It's NO problem when tslib_pibase stays as part of the core! When just 
5% of developers use it, and 95% use lib/div, so what's the problem? 
Everybody has the freedom to decide.

== quality, regarded as necessary components ==
who really does regard componentents as neccesary? really a team? no, 
it's not a team, it's the user. one user is the user of the kickstarter 
who writes a new extension, and an other user is the one who installs 
the extension

== kickstarter ==
for the moment the kickstarter DOES use tslib_pibase. it also could 
write base-code for formidable when there were a kickstarter__formidable

also here: there's not a team who says to all developers "you MUST use
tslib_pibase"!

== requirements importance ==
also here: the developer of an extension decides which "world" he/ she 
wants to get in. the way what kickstarter gives in the moment using 
tslib_pibase (nearly no rules), or formidable (some rules), or lib/div 
(some rules).


Thanks for your effort, Elmar! And please be patient :-)

kind regards
Daniel


>> The core-developers are very diligent, much more than me. It's a good
>> decision to just integrate into the core what 95% of the community wants
>> to have in it. So the core is very stable!! That's great!
>>
> 
> I also go for a very slim core. But that requires that extensions/components
> aren't regarded as low quality code on a rubbish dump called TER.
> Extensions need to be regarded as necessary components that build a
> functional product upon the basic layer. And they need to be named as that.
> 
> But the ugly architecture of tslib_pibase and it's mean fostering over the
> years by the core team reviels a mentality, where extension are not much
> more than tedious adnexa, but no components of imporatance. The reactions
> of the core team to our requests show, that the requirements of
> extension/component developers are still of few importance today. For me
> that's a dead-end street in architecture, a dead-end street in mentality,
> and also a dead-end street for a community, cause there is no option to
> grow.
> 
> Eclipse is taking the component way, OpenOffice goes the component way. Both
> build upon a slim basic layer. Both have workgroups for different
> components. Sure. It's more difficult to synchronize, more difficult to
> oraganzie, but IMHO it's a necessary setup for a framework that perpares
> for the growing demands for future web applications.
> 
> Regards
> 
> Elmar
>