[TYPO3-dev] Adaptation of stg_clearcache to core

[Frank Gerards]

Hi,

>Yes, I am :) I try to be as slim as possible in such cases. Even if the ext is inactive, it can cause problems. >For example, in the past some inactive extension were used for creating security issues. Therefore, the less >you have, the more secure you are. Also, the less you have, the less you have to update (saves you time and >money). Sometimes we have to release core because of issues in core sysexts. The less of them we have, the less >such cases we would have.

That is true and I agree from a programmers point. But, removing all possible sysext from the core means also loosing core features, which might be interesting to customers. Ofc you can tell them "TYPO3 can do this", but at least bigger companies tend to mistrust "features added by extensions", so I would be careful not to remove features from an enterprise CMS, which has feature-richness as one of its biggest assets. Don't forget decisions are not always made from only a rational point of view, but also from an intuitive or emotional one. And as far as this is concerned, "built-in" means a lot more safety then "added by extension", regardless of what the technical background is.

Just my 2 cents,
Frank

-----Ursprüngliche Nachricht-----
Von: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-bounces at lists.typo3.org] Im Auftrag von Dmitry Dulepov
Gesendet: Samstag, 14. Juli 2012 20:00
An: typo3-dev at lists.typo3.org
Betreff: Re: [TYPO3-dev] Adaptation of stg_clearcache to core

Hi!

Philipp Gampe wrote:
> If you want a slime core, then start about dropping no essential stuff like:
> * linkvalidator
> * import/export
> * indexed search
> * BE news
> * task center
> * reports
> * configuration (the module)
> ...

If I could, I definitely would. May be I will keep reports and config because they are important for troubleshooting. The rest is definitely not needed in the core.

>> If you need an ext, just install it from TER. Or make a copy of the 
>> core and put exts you use to typo3/ext. As far as I know, most big 
>> TYPO3 companies do that.
>
> That is not the point, is it?

Yes, it is. This is why it is the core. It is like a kernel: it comes naked but you can also have additional stuff as drivers or kernel extensions. The slimer the kernel, the better. Fat is always bad, regardless where it is.

> We should try to ship a core that is usable to the average integrator, 
> not one that is a boilerplate for big companies customization.

That's right. But it does not mean we need to put there stuff you or me thinks are useful for everybody because it is usable for you and me. You and me and everybody else can get it from TER. That's the point of TER.

> That is my opinion and I know you are more a purist in this regard.

Yes, I am :) I try to be as slim as possible in such cases. Even if the ext is inactive, it can cause problems. For example, in the past some inactive extension were used for creating security issues. Therefore, the less you have, the more secure you are. Also, the less you have, the less you have to update (saves you time and money). Sometimes we have to release core because of issues in core sysexts. The less of them we have, the less such cases we would have.

--
Dmitry Dulepov
TYPO3 core team member
Blog: http://dmitry-dulepov.com/
Twitter: http://twitter.com/dmitryd

Simplicity will save the world.

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev