The point was to be used as a colloquialism to address people who disagree and encourage them to stop, think and remember everything has tradeoffs and compromis

The point was to be used as a colloquialism to address people who disagree and encourage them to stop, think and remember everything has tradeoffs and compromises. Then to think about those before simply saying "this isn't a GIL workaround". Maybe it had the opposite effect. :) I mean, I'm a python fan and this has tradeoffs too (external dependency, task dispatch latency) which doesn't make it suitable every time the GIL gets in the way. In any case, I don't believe either of these were any more sensational than some of the content in this post.