LISPs had dynamic scoping for this decades ago and it fell out of fashion. I think a large part of that is because in practice it turns the code into spaghetti, and you can make it much simpler by just adding the "context" as a function argument. No special language features needed.
When everything is scoped dynamically, it is indeed a problem. If you only have a handful of things with a clear syntactic mechanism to indicate when they are being used? Much clearer.
I impkemented a slow version of contexts in Smalltalk, just to see how bad it was. Where it shone was in places where you can't pass a context as an arg (eg. binary math operators) either for compatibility reasons or because passing the context would be too noisy.
I disagree it's clearer, because it's a spooky action at a distance. An analog are thread locals, which have the same characteristics of a dynamically scoped variable.
I've found dynamic scoping useful so few times I can count them on one hand, and while it's an intriguing feature, I think it makes a lot of sense to use a more explicit abstraction. For example, you shouldn't need dynamic scoping for overloading binary operators - you should have a more clear method that takes a context as an argument instead.
Context is external state, and it's extremely surprising when a fundamental operator like "+" modifies it.
