While they're at it, they might as well check if their answers end with a yes/no question, and, if so, offer a "yes" button so that i can answer yes with a single click.

> If you want a focused comparison next - for example, benchmarks on coding/math, token-cost examples for a typical session, or API usage differences - I can produce a compact table with sources and numbers.

--> can be answered with yes, so please add a yes button. A no button is not needed.