Board Thread:Watercooler/@comment-5590118-20150701035141/@comment-3032314-20150703121150

Dessamator wrote: Actually, when writing meta-modules, you'd generally use a more descriptive table name.

This... isn't necessarily true. Take a look at Module:TableTools for example. To get back to the original question, I think naming the global table  is a de facto standard; it's a best practice because people do it, and people do it because it's the best practice.

I think there are three ways we can deal with this situation:


 * 1) Let devs name the global table whatever they want.
 * 2) * Pros: freedom
 * 3) * Cons: consistency
 * 4) The global table should always be named.
 * 5) * Pros: short, follows the de facto standard
 * 6) * Cons: confusing(?)
 * 7) The global table should always be named.
 * 8) * Pros: very clear
 * 9) * Cons: long, doesn't follow the de facto standard

Related question: how do you guys feel about modules that return a single function, e.g. Yesno?