Rather than focusing solely on how much quicker deep access is than superficial access, describe why deep access is preferable from the developer's perspective

The _____suggests splits interfaces that are very large into smaller and more specific interface so their clients will only have to know about the methods that are of use to them. (SRP, OCP, LSP, or ISP?) The Single Responsibility Principle (SRP)The Open-Closed Principle (OCP)The Liskov Substitution Principle (LSP)The Interface Segregation Principle (ISP)The Dependency Inversion Principle (DIP)

Provide a programmer's viewpoint on why deep access is preferable to shallow access, rather than focusing just on performance.

Don't just argue performance-explain why programmers prefer deep access over shallow access.

Don't just argue that deep access is superior because it's faster; provide concrete examples of how a programmer might benefit from it.

Instead of focusing purely on performance, explain why deep access is preferable to superficial access from a programming perspective.

Explain why, from the point of view of a developer, deep access is preferable than shallow access, rather than relying only on performance considerations.

An interface's limitations may be severe. When a user can't access the Windows desktop or the Internet, for example, the interface design may be restrictive. Is it appropriate for a user interface to impose such limitations? Is there a reason for this or not?