Another optional core feature

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Another optional core feature
« Reply #30, on October 9th, 2011, 06:47 PM »
I was going through the old topics in this board and came upon this one.

Having actually modified how custom profile fields work, I can say that in reality this was even more misguided than I suspected before; the amount of performance change by disabling CPF was negligible - but not because of inefficiency.

In fact, a cached version of the fields to use was stored and immediately available, so if CPFs were disabled, the code simply wasn't run.


I do see the point being made, and interestingly here we are 6 months later and having had a discussion about this very point, as has been discussed only today about splitting off the PM and memberlist features into their own plugins.

I think, though, that the way the discussion was reached was absolutely in spite of the above crap, and solely because it was noted that the plugin manager would make it vastly more feasible to make these things plugins.

Interestingly, even with the power of the plugin system, I can't really see CPFs being a plugin, or indeed some of the other 'more core' features, simply because while yes there is a benefit to be had, there are other things that have to be given up to achieve it.
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial