> Cuis has a PerformanceImprovements package that holds the fast but
difficult to understand versions of methods that use simpler but slower
versions in the base image. Maybe that idea could be adopted?

A central package for performance improvements would violate the idea of information hiding and hence impede modularity unless there would be such a package for each specific domain (e.g., CollectionImprovements, KernelImprovements etc.) ... but even then ... if any, extra versions of particular methods should be as close to the original artifact as possible. When programmers would stumble upon a hard-to-understand method in the code browser or debugger, the respective tool should point to the more readable version. And the other way around. I think. :-)

Best,
Marcel
Am 22.02.2021 11:11:12 schrieb Douglas Brebner <kirtai+st at gmail.com>:
On 20/02/2021 20:51, Levente Uzonyi wrote:
> My stance on library methods is that they need to be optimized because
> you don't know how people will use them. If they are fast, people will
> be happy. If they are not, you'll leave a bad impression.

Cuis has a PerformanceImprovements package that holds the fast but
difficult to understand versions of methods that use simpler but slower
versions in the base image. Maybe that idea could be adopted?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210222/fa8c8f4c/attachment.html>