Can you give examples of classes in UIKit that violate SOLID principles?

UIKit has several classes that are often criticized for violating SOLID principles, especially the Single Responsibility Principle. For example:

• UIViewController — a class that often becomes a "god object" containing display logic, user event handling, network requests, navigation, etc. This violates the Single Responsibility Principle.

• UITableViewCell — sometimes contains UI setup logic and business logic, which also mixes responsibilities.

• UIApplicationDelegate — often overloaded with a lot of code responsible for different aspects of the application's lifecycle.

Overall, UIKit provides powerful classes, but the responsibility for adhering to SOLID lies with the developer, who should separate logic and avoid overloading classes.