Dynamic

Duck Typing vs Interface-Based Programming

Developers should learn duck typing when working in dynamically-typed languages to write more generic and reusable code that focuses on what objects can do rather than what they are meets developers should use interface-based programming when building modular, maintainable systems, such as in large-scale applications, microservices architectures, or when implementing design patterns like strategy or adapter. Here's our take.

🧊Nice Pick

Duck Typing

Developers should learn duck typing when working in dynamically-typed languages to write more generic and reusable code that focuses on what objects can do rather than what they are

Duck Typing

Nice Pick

Developers should learn duck typing when working in dynamically-typed languages to write more generic and reusable code that focuses on what objects can do rather than what they are

Pros

  • +It's particularly useful for creating flexible APIs, implementing design patterns like strategy or adapter, and handling diverse data structures in a uniform way, such as iterating over collections regardless of their specific type
  • +Related to: dynamic-typing, polymorphism

Cons

  • -Specific tradeoffs depend on your use case

Interface-Based Programming

Developers should use interface-based programming when building modular, maintainable systems, such as in large-scale applications, microservices architectures, or when implementing design patterns like Strategy or Adapter

Pros

  • +It is particularly valuable in scenarios requiring unit testing with mocks/stubs, supporting multiple implementations (e
  • +Related to: object-oriented-programming, design-patterns

Cons

  • -Specific tradeoffs depend on your use case

The Verdict

Use Duck Typing if: You want it's particularly useful for creating flexible apis, implementing design patterns like strategy or adapter, and handling diverse data structures in a uniform way, such as iterating over collections regardless of their specific type and can live with specific tradeoffs depend on your use case.

Use Interface-Based Programming if: You prioritize it is particularly valuable in scenarios requiring unit testing with mocks/stubs, supporting multiple implementations (e over what Duck Typing offers.

🧊
The Bottom Line
Duck Typing wins

Developers should learn duck typing when working in dynamically-typed languages to write more generic and reusable code that focuses on what objects can do rather than what they are

Related Comparisons

Disagree with our pick? nice@nicepick.dev