Your last point really resonated on the Django example for RequestContext - the entire point of using a framework is taking advantage of the set of tools and co

Your last point really resonated on the Django example for RequestContext - the entire point of using a framework is taking advantage of the set of tools and conventions it provides, and that code is basically reinventing the Django settings module. It’s almost always going to be better to write the simple standard code, or to pick an example which doesn’t start with an incorrect assertion to justify the extra complexity it’s adding. It does also make me wonder whether part of the problem is that they’re not used to a language with keyword arguments - passing a single parameter through a nested function call really shouldn’t get that strong negative reaction. In general, this reminds me of the common problem where people assume their code will be reused far more often than it actually is and try to write code like the frameworks they’ve learned without considering whether they have the same resources to develop their new bespoke framework.