In reply to Ed.

(Please post this response to Ed which I believe makes how I see it clearer than the previous one).
Hi Ed,
I don’t mean at all to be understood as saying that WP-Optimize has no room for improvement, or no room for improvement around the discussed feature. Not at all. As per my comment, we’ll certainly want to look at the feature using our normal development processes. “Nothing to see here” is absolutely not what I want to be heard as saying. We respond to all users’ support requests and ideas and are grateful for them. They’re an important part of improving.
What I’m responding to here, under this article, is specifically (and really, only) the Twitter poster’s offensive framing that WP-Optimize is deliberately evil and should be abandoned (preferably for his products). He’s managed to induce WP Tavern to run two articles under that framing of the issue, and managed to induce his Twitter followers to propose that the plugin directory should cancel our plugin. That’s why I’m here. (I’m assuming most people wouldn’t like to see that in their daily feeds).
We have channels for discussing plugin development and features in normal ways. But under the framing of deliberate cheating, that’s what I came here to discuss – to refute a direct and public competitor attack that successfully induced WP Tavern to then re-publish the allegations and get them syndicated to every WordPress install on the planet via the news feed. Ouch. Other issues, as I say, fine. But in their proper channels, not as part of a public spat under the current framing, I’m not up for that. That’s not running away – it’s not actually my normal role to discuss precise UI implementations anyway, as I’ve said, our main WP Optimize JavaScript expert is someone else.