I see a few issues/arguments that pop up and never get resolved in these Context threads.
-
Real examples that have 20+ schemas, 20+ endpoints, real use cases and real business requirements. This is probably the number one thing that will help the community with this problem. It is still early, so I’m sure that this will come in time.
-
Not acknowledging that a large part of web application development is simple crud. The problem is that contexts add ceremony with little value.
-
Pretending that the mess made with contexts will be a better mess.
-
Naming stuff is hard and now we have to name three things the Context namespace, the struct, and then add an interface from the context and the web world.
Most of these are just educational issues that would be better solved by publishing lots of code and blog posts 
However, there is a very real need for a standard “I didn’t know what to name this thing, it doesn’t really matter, stop trying to make it matter, just tell me where to shove the thing so I can get back to shipping features.” I think that providing a good enough guideline for the community would yield the incremental change that we need to move forward.
