> if you find yourself needing deep accessors, something is very wrong with your scopes I'm not sure I agree with that statement in all scenarios. For code you

> if you find yourself needing deep accessors, something is very wrong with your scopes I'm not sure I agree with that statement in all scenarios. For code you control, sure. But there are many APIs that return very deeply nested structures that are inconsistent in their shape. That, in my view, is the most common place devs will need deep accessors where parts may be null/undefined somewhere in between the root object and the key they are trying to access. Sure, they could write functions that, similar to get in lodash, expose just the values needed, at which point chaining wouldn't be needed at all in the code that deals with that value. Or it could be serialized into a class object, but again, the chain would be dealt with in the serialization. At some point, the chain needs to be dealt with and often the JSON structures from APIs are not something that's always under our control.