" Say I'm giving away my lemons and someone opens a profitablt mystery-drink stand just around the corner. "
I'd be curious, wouldn't you? The original lemons-to-lemonade illustration was misinformed to gain rhetorical advantage. Seeing a self-evident lemonade stand across the street is all the information a GPL advocate would require. No attempts to govern recipe or even price would be made - I'd simply know what it is.
---
Real world experience: I need GPL (v3!) and more. It's absurd to think someone can't learn by reading my public "code" -whatever the license- but my "projects" also suffer vigorous scamming in their entirety. (Whiteout-ware, malware-injected redistributions, even selling my original untouched binaries as their own. Extensive uncredited reuse in Chinese outsourcing, plus real corporate identity-theft with no reuse of any code at all.) As a practical matter I want to best protect my users, even if I have no real objection to blocks of code ending up just about anywhere useful.
Oh, and adding a lot of ancillary Creative Commons Attrib-NonCommerical-ShareAlike artwork helps protect the "project" while freeing the "code." But no license protects against people who disregard them.