Difference Between "Takes" and "Suggestions" Thread
Posted: Fri Dec 09, 2022 8:52 am
Over the past week, I have come to understand that many posters are using the word "take" and "idea" interchangeably. Even I, the ever-knowledgeable Farquaar, have likely done so on at least one occasion. Thus, it behooves us to ask: what is the difference between an idea/suggestion and a take? I posit that a take is inherently reactive, while suggestions are inherently proactive. Allow me to make my case:
Dictionary Definitions:
It appears that "take" is inherently reactive as it is restricted to a personal point of view on extant subject matter, typically something that has recently changed. An idea or suggestion, on the other hand, may comprise purposive suggestions or directions.
If we abide by this dichotomy, then most "takes" presented over the past week are not "takes", but rather "suggestions". Allow me to construct some examples:
Discuss.
Dictionary Definitions:
► Show Spoiler
If we abide by this dichotomy, then most "takes" presented over the past week are not "takes", but rather "suggestions". Allow me to construct some examples:
This is an prima facie take. It is an mere opinion- a reaction to something that happened- a change in game mechanics.Poster A wrote: Removing cloning was a mistake
This is an idea. A suggestion. A formulation of a plan of action for the game designers that has never been tried.Poster B wrote: Stun batons should permanently break after ten uses.
A take. It reacts to the removal of Clock Cult, something which happened in the past.Poster C wrote: We should readd Clock Cult to the game. It was cool.
Also a take. Recency bias is not determinative with respect to the dichotomy.Poster D wrote: We should remove Blood Cult from the game. It sucks.
An archetypical suggestion. Unless Ian had laser eyes in the past, or there were serious discussions regarding the addition of corgi laser eyes, there is nothing being reacted to.Poster E wrote: Ian should have laser eyes.
Discuss.