[TYPO3-core] RFC #11606: [Feature]: Add a RANDOM cObject

Michael Stucki michael at typo3.org
Tue Aug 4 17:12:10 CEST 2009


Hi Dmitry,

> I am not sure about official. What I want to say is that we should
> get only the best code to the core. Recently TYPO3 core quality
> degraded severely. 4.2.0 was the last version, which was more or less
> acceptable in terms of quality. Now clients ask me NOT to upgrade
> TYPO3 anymore because they hate to fight more and more problems in
> newer TYPO3 versions. Therefore, if I were in the core team
> management (but I am not!), I would enforce very strict rules for any
> code committed to the core. Better less but with higher quality.
> Otherwise TYPO3 will drop to phpBB level at some day. I do not want
> this to happen.

I think we have different understandings about the health of TYPO3. I
agree that quite a few people are getting more and more lazy, trying to
be as fast as possible. This can be noticed by the amount of
post-commits, spelling fixes in the changelog, etc.

In this regard, I share some of your concerns. I think that we should
always aim for getting rid of these mistakes. However, the fact the the
issues still get fixed means that there is still a working quality
assurement running in the background. That is mostly Olly, Ingo and me,
checking every changeset and doing fixes every now and then.

A loss of quality would in fact mean that TYPO3 4.2 contains more bugs
than 4.1 did. My impression is that the number of reported bugs has
constantly increased during the last years, but most of the issues are
not 4.2 only but affect also older versions.

> Regarding RANDOM object, I estimate that it will take approximately
> extra 15 lines of code to make it well. "Well" means: - it is truly
> random for all times, even when cached - it does not force users to
> write absolutely unnecessary COA_INTs to make the object behave
> properly (=show random element) - it is faster than the COA_INT
> version

I agree about this but for consistency (which is also part of the
quality IMHO), I would wait for a more general solution to do this,
which also works for TEXT cObjects for example.

And, Krystian already gave a good example for why RANDOM being cached
may still make sense.

- michael

-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/


More information about the TYPO3-team-core mailing list