[Typo3-dev] singletons instead of pre-loaded objects

[Kasper Skårhøj]

On Thu, 2004-08-12 at 15:06, Leendert Brouwer [Netcreators] wrote:
> Hi Kasper,
> 
> > But I do agree with many of Leenderts points, but the discussion just
> > reminds me of all the insufficiencies, rather than motivates for change.
> > I haven't had a single "Oh, I never though of that" moment in this
> > thread, only a very discouraging feeling that I rather want to leave it
> > all and do something else in my life. Remember; 5-6 years of dedicated
> > development on a single thing, having sacrificed a lot for the sake of
> > the project (=all of you); It is of course rewarding but no dance on
> > roses. It has worn me out, made me tired and subjectively sensible. Each
> > time I try to tell you all "Focus on extensions, focus on extensions" it
> > is because I want to divert you away from this itchy, negative spot and
> > focus on the area where the positive opportunities for the future are!
> 
> I'm sorry if I upset you in any way, I never meant to. 

I don't get angry, but it always hurts a little and distracts me a lot.
I see that as a weakness in me because I don't want to discourage a
sound discussion. I mostly point this out because it would be nice if
the list knows that harsh discussions over the well-known and agreed-to
deficiencies of TYPO3 doesn't help us anywhere.


> I'm just a developer,
> I'm interested in technology more than statistical succes. I'm personally
> more interested in engineering theory than in anything else. That's probably
> why I sound negative. Obviously TYPO3 has a lot of success. Thousands of end
> consumers are very grateful, I'm sure. Disregard the light some meaningless
> coder sheds on the lesser aspects of the core architecture and do your
> thing, I'd say. Yes, a core rewrite is a massive amount of work, and I
> wouldn't suggest it either. I'm just telling things as I see them, and
> describe things I run into when I have to override core behaviour in my
> extensions.

OK,

I think all of this is relative. Again; I can understand your points but
TYPO3 is not successful because we ignore good design. There are plenty
of testimonies from people who think this is the best software they have
ever seen! Of course that is not true, but compared to other products
TYPO3 is very beautifully coded! And this also seems to attract people!
(based on "eye-witness accounts"!)

We don't have success in terms of user-counts anywhere near phpNuke I
think or phpMyAdmin, but I think that we deserve our success mostly
because we have a good product that offer value for money and where time
has proven that it didn't collapse.

> My own extensions are fully OO. Some even have accompanying unit tests and
> so on. I run into trouble when I have to override core behaviour, or try to
> find out things, or when I need to learn things about the system. It's just
> hard because for me, the architecture is not intuitive. But we already
> discussed that.

I hope your work can inspire others. It could be the "Leendert-school of
TYPO3 Extension Programming". By time TYPO3 might even be considered a
mainly OO-designed application except the core parts - but where the
core parts has declined in significance because the surrounding
extensions has gradually taken over more and more important "core"
operations!


> 
> Apparently it's sufficient enough, or else not that many sites would be
> running TYPO3. Again, I'm just a developer. I don't think I experience the
> end-user experience. It's like living in a house that is fine to live in,
> just not really practical to modify and see through afterwards when you're a
> carpenter. I'm the annoyed carpenter :)

And the rest of us are romantics, liking the patina of "good ol'e
TYPO3"...


Have a nice evening!

- kasper