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

[Dmitry Dulepov]

Hi!

Fabrizio Branca wrote:
> Why is a cached random object not working properly in your opionion?
> There are scenarios where this makes absolutely sense.

Because it is not random: it will show the same object each time.

> If you say that wrapping around a COA_INT is way to slow we should go
> for a RANDOM and a RANDOM_INT object. But how often do people wrap
> things into COA_INTs when they want them not to be cached? Wouldn't that
>  for example mean to have a TEXT_INT too (for those who want to display
> the current time via typoscript...)?

I am not ready to answer about TEXT_INT but wrapping anything to the COA or COA_INT without real purpose is a bad idea.

>> TYPO3 quality sucks these days.
> 
> It is not fair to generalize this statement. Think of all the people
> putting so much effort into the TYPO3 code in their free-time! Saying
> that their code sucks might stop them from wanting to contribute code...
> Please be careful with statements like these.

It is fare because it is truth. I also put a lot of my free time into TYPO3 core and major extensions. I think I put more than many others. According to SVN statistics I was the topmost contributor to 4.2.0 core. Therefore I have all rights to say what I say. Hiding the truth will not improve quality at all. It is bad to say that all is fine when there are problems. Hiding problems will not solve them but make them worse.

TYPO3 quality seriously degraded over the last year and it already causes customers to search for other CMSes. If you did not encounter this already, you are lucky.

I am not really going to argue about all this. If you think that all is perfect, please do. It is your choice.

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