Re: Speeds vs functionality

How much speed are you willing to sacrifice for a new feature?

If it's a feature I don't want none. If it's a feature I do want as little as possible.

I guess it's a balancing act between the number of people who want the feature, how much they want it, and what everyone who doesn't want it will accept before forking the module.

Comment on Re: Speeds vs functionality

Replies are listed 'Best First'.
Re^2: Speeds vs functionality by Tux (Canon) on Aug 04, 2014 at 09:31 UTC
None sounds a bit selfish. Understandable, but not realistic. No single product (or module) in the public domain is written for just one single user. If it were, it would not be on CPAN. There are no two users that are identical, not even me myself and I. As a module author I somehow expect that the author of CPAN modules do try to minimize performance penalties. Always. So "as little as possible" is - to me - an "of course". The balance I am finding is my prediction in how people/user will need the new feature in the future. My reading of the responses, conversations with other developers and reading comments on related OpenSource projects have made me to decide this is the only way forward. A performance hit of less than 5% is acceptable if I open the usability to a new group that up till now was forced to use slower parsers. The new code performs quite well. The cache code has been simplified and only got me marginal changes: ą 1%, which I interpret as noise. I've been testing with 5.6.1 through 5.21.1 over this weekend and all looks pretty well. Only perl built with strict clang currently fails. I will need to address this before I release. Thank all for the valuable feedback. Enjoy, Have FUN! H.Merijn	[reply]

Replies are listed 'Best First'.

Re^2: Speeds vs functionality
by Tux (Canon) on Aug 04, 2014 at 09:31 UTC

None sounds a bit selfish. Understandable, but not realistic.

No single product (or module) in the public domain is written for just one single user. If it were, it would not be on CPAN. There are no two users that are identical, not even me myself and I.

As a module author I somehow expect that the author of CPAN modules do try to minimize performance penalties. Always. So "as little as possible" is - to me - an "of course".

The balance I am finding is my prediction in how people/user will need the new feature in the future. My reading of the responses, conversations with other developers and reading comments on related OpenSource projects have made me to decide this is the only way forward.

A performance hit of less than 5% is acceptable if I open the usability to a new group that up till now was forced to use slower parsers. The new code performs quite well. The cache code has been simplified and only got me marginal changes: ą 1%, which I interpret as noise.

I've been testing with 5.6.1 through 5.21.1 over this weekend and all looks pretty well. Only perl built with strict clang currently fails. I will need to address this before I release.

Thank all for the valuable feedback.

Enjoy, Have FUN! H.Merijn

[reply]