[Typo3-dev] Welcome back in the "goto-age"?

[Sven Wilhelm]

or standards vs. flexibility...

-- As Michael asked, why this posting in the off-topic list. --


Hi,

don't kick me, it's just my mind after a night of stupid search for 
standard based solutions and I'm tired.

When currently reading code I sometimes feel back to the age where goto 
statements in the code were ok.

xclassing as one example. extending extensions and extending the 
extended extension.

Do the developer not want to work together?

Could many of the "enrich the core with expected 
functionality"-extensions not move the functionality to the core?

Who has an overview of all the side-effects coming with this kind of 
developing?

As I'm an admin on unix-technics for many years now I often remember the 
  kiss-statement (Keep it simple, stupid), and you often have a very 
transparent system in front of you.
Many parts of typo do not follow this statement at the moment.

For new users the first investment is very high.
As a developer it's nice for developing fe-plugins as you have the final 
solution very fast, but coding in the backend? Use libraries for ways 
other than the webbased way?

Are there sometimes reviews of the codebase? Are there release or 
milestone plans, where you now what is currently on the topic list or 
eg. if there is a reengineering for a subsystem planned? Has sometimes 
the benefit to have a codebase which is smaller and faster, eg. direct 
integration of "Authentication Services" (which in my eyes is just a 
php-implementation of the wellknown PAM-System) to the core, not using 
as an extension.

Is there really a need to reach the 100% flexibility? Other software 
systems also have restrictions? Isn't the Eclipse-way just a nice way? 
You have defined Extension points and Extensions which use them for 
connecting additional features. It's clean and documented due the 
xml-file in the plugin.