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

Dmitry Dulepov dmitry.dulepov at gmail.com
Sun Aug 2 20:51:53 CEST 2009


Hi!

Mathias Schreiber [wmdb >] wrote:
> Dmitry Dulepov schrieb:
>> Either do it well, or do not do it at all.
> 
> Could we make this statement oficial in some way? :)

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.

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

So, what would you choose of the following two:
- true random RANDOM object, which is automatically non–cached
- RANDOM object, which is not random by default and forces users to use COA_INT to make it truly random (=work properly)

My choice is #1 because I always use that principle: "Do it well or do not do it at all". If you create a RANDOM object, do it properly!

TYPO3 quality sucks these days. I do not want it to become even worse.

I am not talking on behalf of the core team right now. I am talking as a private user.

-- 
Dmitry Dulepov
LinkedIn: http://www.linkedin.com/in/dmitrydulepov
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs


More information about the TYPO3-team-core mailing list